Related
Hello everybody,
I could use some help with my Ace 2, which I somewhat broke today in the process of installing CM. It was quite a mess, but I'll try to outline the general steps I took.
As you can probably tell, I am rather new to this and I'm afraid I've done some irreparable damage, so I'd appreciate any support I can get.
Plan: Install Cyanogenmod on Samsung Galaxy Ace 2 GT-I8160.
Phone Region: Germany
Phone OS: Never updated since factory shipping (Android 2.2?), rooted
PC OS: Linux (Ubuntu 16.04) (ergo Heimdall only, no Odin)
1. Found https://wiki.cyanogenmod.org/w/Unofficial_Ports, followed link under "Samsung Galaxy Ace 2 (GT-I8160)" - "CyanogenMod 11 " to http://forum.xda-developers.com/showthread.php?t=2568105
2. Followed forum op link to http://novafusion.pl/, search for "Ace 2" brought up http://novafusion.pl/2014/03/10/release-cm11-0-2-ace-ii/
3. Went to "Downloads" Section, selected "Samsung Galaxy Ace II", "Cyanogen Mod" and "recovery" from the respective drop-down menus, downloaded it.
4. Copied cm11.0_codina.nova.20141215.zip to SD, started phone in recovery mode
5. "Android System Recovery <3e>" could not open SD card/listed external SD as empty directory
6. Installed CWM, wiped cache/factory reset from recovery menu, installed cm11.0_codina.nova.20141215.zip from SD
7. Phone booted into CM, everything worked except things phone-network/SIM-related, error-prompt every few seconds: "Unfortunately the process com.android.phone has stopped", SIM contacts could not be accesed, could not call or receive calls
8. Went looking for different ROM, found http://forum.xda-developers.com/galaxy-ace/ace-2-develop/rom-cyanogenmod-12-1-09-04-15-t3201826
9. Downloaded "CyanogenMod12.1_I8160_0920.zip" and installed from SD in CWM
10. Still no mobile network, SIM card unlock prompt kept coming up -> couldn't unlock SIM card, error message in notification-area: "No SIM card detected, Emergency calls only", carrier was not displayed on home screen, all settings said "No network connection" or similar
11. Researched, found various posts saying upgraded stock rom is required before flashing custom ROM (e.g. here: http://forum.xda-developers.com/galaxy-ace/ace-2-general/ive-broken-phone-t3442544) and http://ask.drprem.com/q/samsung-galaxy-ace-2-gt-i8160-no-network-after-cyanogenmod-10-2-flashing advised flashing modem file from stock firmware
12. Downloaded DBT-I8160XXNB1-20140312182944.zip stock firmware, extracted I8160XXNB1_I8160OXXNB4_HOME.tar.md5, removed .md5 from filename and extracted again (because Heimdall needs the individual .img.md5/.bin.md5 files), resulting in 9 files: cache.img.md5, hidden.img.md5, ipl.bin.md5, kernel.bin.md5, mem_init.bin.md5, modem.bin.md5, normal.bin.md5, power_management.bin.md5, system.img.md5
13. Used Heimdall to flash modem.bin.md5 to phone in hopes of fixing network-issue, but no change when booting, everything works but still no mobile network etc.
14. Tried to go back to stock firmware alltogether to start from scratch, by flashing all the other files from the download with Heimdall
15. Now the phone does not boot up at all, gets stuck at the "Samsung Galaxy Ace 2 GT-I8160" logo screen, recovery mode can not be accessed, download mode still works, can only be switched off by removing battery
16. Tried to get recovery mode working again by installing TWRP from here: http://forum.xda-developers.com/showthread.php?t=2532591, downloaded file and extracted kernel.bin.md5 (just like in step 12), flashed to phone with Heimdall -> No change, still stuck on logo screen without recovery mode
17. Tried to follow this guide to go back to original version: http://www.droidviews.com/how-to-downgrade-galaxy-ace-2-gt-i8160-to-gingerbread-from-android-4-1-2/, downloaded CODE_GT-I8160P_I8160PXXLK2_REV00_SEC_KEY_4G.rar, unpacked everything, unpacked .tar.md5 files, flashed everything to phone with Heimdall from command line -> No change, still stuck on logo screen
I imagine there is quite a mess of various partitions of various versions and varios OSs on there by now.
Did I brick the phone? Is there any way to restore it?
Since download-mode is still working, I could imagine that some form of Heimdall-wizardry might help, but things are way out of my league at this point.
Can anybody help me here?
Thanks in advance!
Solved it.
Installed W7 and Odin on spare drive, then followed this guide: http://forum.xda-developers.com/galaxy-ace/ace-2-develop/ace-2-baseband-xxxx-repair-t2823218
After that, I went through the regular ROM installation process and everything works now.
With access to Odin it's surprisingly ezpz.
I have an old Z00A that has hardware problems (constant screen flickering, battery stuck at 50%) so I backed up every partition with TWRP including system, boot , data etc and purchased a new Z00A.
I used the new Z00A for a few days to ensure that there was no hardware problems and then proceeded to unlock the boot loader and flash TWRP recovery. At this point both sims were working.
I then restored the backup of the old Z00A with TWRP on the new Z00A (Had to change folder name so TWRP recognizes the backup from the old Z00A). After the restore was complete and the phone booted, sim1 stopped working.
After searching through the forums and Google I found some solutions to it but none of them seem to work
Solutions that I have tried
1. Factory reset the phone through TWRP
2. Wiped every partition through( exclude SD Card) TWRP, flashed stock recovery and installed the official firmware.zip file through stock recovery
3. Did a factory reset with the stock recovery flashed (skimmed through the setup)
4. I downloaded the latest RAW file firmware and installed it through ASUS Flash Tool (Had some issues at first but eventually it went through but sim1 doesn't work)
5. I installed the official Lollipop rom through fastboot and flashed a custom Lollipop rom
6. Flashed stock based MM rom (CleanStock), custom MM and N roms (CM, Lineage, RR) through TWRP and do factory resets
7. I have tried using the adb shell and root commands to set the IMEI but they still return to 004999--------
8. Placed the sims in the old Z00A and they still work
9. Swapped the sim trays of both phones (sim1 and sim2 works on old Z00A but sim1 still doesn't work on new Z00A)
10. Used phonetools to set IMEI but they still return to 004999--------
From flashing the custom roms and swapping the sim trays I can conclude that this is not a hardware problem. On most custom roms it recognizes that there is a sim inserted in sim1 (A pop up comes up about sim has changed etc...) but there is no signal and the phone says emergency calls only or no service. I believe that the baseband or modem file are somehow corrupted due to the TWRP restore from the old Z00A and need to be reflashed but this only seems possible on the Snapdragon variant.
All help is appreciated on this matter :fingers-crossed:
Captain Krunch said:
I have an old Z00A that has hardware problems (constant screen flickering, battery stuck at 50%) so I backed up every partition with TWRP including system, boot , data etc and purchased a new Z00A.
I used the new Z00A for a few days to ensure that there was no hardware problems and then proceeded to unlock the boot loader and flash TWRP recovery. At this point both sims were working.
I then restored the backup of the old Z00A with TWRP on the new Z00A (Had to change folder name so TWRP recognizes the backup from the old Z00A). After the restore was complete and the booted, sim1 stopped working.
After searching through the forums and Google I found some solutions to it but none of them seem to work
Solutions that I have tried
1. Factory reset the phone through TWRP
2. Wiped every partition through( exclude SD Card) TWRP, flashed stock recovery and installed the official firmware.zip file through stock recovery
3. Did a factory reset with the stock recovery flashed (skimmed through the setup)
4. I downloaded the latest RAW file firmware and installed it through ASUS Flash Tool (Had some issues at first but eventually it went through but sim1 doesn't work)
5. I installed the official Lollipop rom through fastboot and flashed a custom Lollipop rom
6. Flashed stock based MM rom (CleanStock), custom MM and N roms (CM, Lineage, RR) through TWRP and do factory resets
7. I have tried using the adb shell and root commands to set the IMEI but they still return to 004999--------
8. Placed the sims in the old Z00A and they still work
9. Swapped the sim trays of both phones (sim1 and sim2 works on old Z00A but sim1 still doesn't work on new Z00A)
10. Used phonetools to set IMEI but they still return to 004999--------
From flashing the custom roms and swapping the sim trays I can conclude that this is not a hardware problem. On most custom roms it recognizes that there is a sim inserted in sim1 (A pop up comes up about sim has changed etc...) but there is no signal and the phone says emergency calls only or no service. I believe that the baseband or modem file are somehow corrupted due to the TWRP restore from the old Z00A and need to be reflashed but this only seems possible on the Snapdragon variant.
All help is appreciated on this matter :fingers-crossed:
Click to expand...
Click to collapse
very first of all root your device. install any root explorer like es file explorer. enable root explorer and hidden files in options of file explorer.
now go to root storage of device meas (/)
find factory folder in factory go to telephony folder and take screenshot
find config folder and then go to telephony folder and take screenshot
post screenshots here then we will look further
sukhwant717 said:
very first of all root your device. install any root explorer like es file explorer. enable root explorer and hidden files in options of file explorer.
now go to root storage of device meas (/)
find factory folder in factory go to telephony folder and take screenshot
find config folder and then go to telephony folder and take screenshot
post screenshots here then we will look further
Click to expand...
Click to collapse
Screenshots posted
Captain Krunch said:
Screenshots posted
Click to expand...
Click to collapse
flash debug firmware and use intel phone tool
sukhwant717 said:
flash debug firmware and use intel phone tool
Click to expand...
Click to collapse
Can you link me to this debug firmware please?, I have already found the Intel phone flash tool
Captain Krunch said:
Can you link me to this debug firmware please?, I have already found the Intel phone flash tool
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B72QQTXqZSRwTmZoQXZxZ0tvTmc
sukhwant717 said:
https://drive.google.com/open?id=0B72QQTXqZSRwTmZoQXZxZ0tvTmc
Click to expand...
Click to collapse
Thank you very much, after flashing this firmware how do I proceed?, I am currently downloading it and hopefully it flashes successfully
Mods can close this thread as he helped me resolve the issue through PMs
Same issue what to do?
Sent from my AO5510 using XDA-Developers Legacy app
My problem was because of a wrong IMEI, I had to flash the debug firmware he linked above and use phone tools 191 to change the IMEI then sim1 began working.
Send me that tool
mkaraniya said:
Send me that tool
Click to expand...
Click to collapse
Tools: https://yadi.sk/d/30q9w4KJjvgHd
You can also watch this video to help you use the tools: https://youtu.be/5oxug7ThayM
Hi everybody,
I also have a problem with sim card , but it is a little bit different then these that have been described above. First of all my sim is working but not all of the time. I do calls and also I receive a lot of calls. But from time to time sim card just restarts and wants again pin code to unlock ( the phone doesn't restart). A lot of people told me that when they are trying to connect me, their phones are ringing twice and after that they heard busy signal as the call was rejected or the line is busy. In the same time my phone doesn't show any incoming call. Also it is interesting that some people told me that they can't connect me for the hole day and in the same time there is no problem with receiving other calls. From time to time I also can't dial a number. The screen stacks on dialing screen for app. 30 seconds and after that just switch to contacts list.
So what I tried till now:
1. I did a clean install of OTA WW_4.21.40.327
2. Tried to use Sim2 slot, the problems didn't disappear
3. I changed my sim card with new one with no result
4. Tried the sim card with other phone, everything works fine
May be it's time to buy a new phone, but before that I want to be sure that the problems are not caused by software bug.
Any advices and help will be appreciated.
P.S.
The phone is rooted, Magisk 13.3 is installed. The phone is ZE551ML, Z00AD
Captain Krunch said:
Tools: https://yadi.sk/d/30q9w4KJjvgHd
You can also watch this video to help you use the tools: https://youtu.be/5oxug7ThayM
Click to expand...
Click to collapse
is your phone fixed now?
i have the same problem with my lenovo p90 (missing imei). but i cant enabled its com port (no way to fix it with intel phone tool without com port existed). no reference to enable it (the com port) nor imei repair on lenovo p90.
i need you to enter your phone with adb shell as root, and create image of /dev/block/mmcblk0p3 and /dev/block/mmcblk0p5. or just copy config and factory folder, then zipped them, then shared here. i need them, to restore what I accidently erased (config and factory partition).
trust me, i won't do any harm to your specific data.
you're my last hope. i hope you'll understand.
dejoebad said:
is your phone fixed now?
i have the same problem with my lenovo p90 (missing imei). but i cant enabled its com port (no way to fix it with intel phone tool without com port existed). no reference to enable it (the com port) nor imei repair on lenovo p90.
i need you to enter your phone with adb shell as root, and create image of /dev/block/mmcblk0p3 and /dev/block/mmcblk0p5. or just copy config and factory folder, then zipped them, then shared here. i need them, to restore what I accidently erased (config and factory partition).
trust me, i won't do any harm to your specific data.
you're my last hope. i hope you'll understand.
Click to expand...
Click to collapse
Am sorry but I recently sold my ZF2 and currently awaiting a new phone. Am sure someone else on the P90 forums can help you get the files you are looking for
Hey guys,
I would appreciate your help here.
I've flashed NitrogenOS Oreo and set a pattern to run on startup (encrypted).
After I've rebooted the phone the pattern stopped working, the pattern kept working in TWRP.
Methods I've tried to resolve the issues:
- Tried to remove all lockscreen's related file according to the following ( https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008 ) .
- Cleaned flash another rom
- Cleaned flash a backed up rom
- Factory reset
- Updated to the latest blu spark recovery
- Tried flashing Cardinal Xtended
the result is the same - the rom does not accept any pattern, TWRP accepts all pattern, no files exists in /date/system
What am I missing here? this is the first time i'm running into this kind of bull****
EDIT: Seems like an hardware issue, the internal sdcard is totally not recognized after a format from fastboot
edit #2: got resolved, thanks.
go to recovery > wipe > format data > type yes > done > reboot
ele95 said:
go to recovery > wipe > format data > type yes > done > reboot
Click to expand...
Click to collapse
tried that amigo, thanks.
nimrodsv said:
tried that amigo, thanks.
Click to expand...
Click to collapse
Tried using the mega unbrick method 2?..
Usually fixes many broken issues
nimrodsv said:
Hey guys,
I would appreciate your help here.
I've flashed NitrogenOS Oreo and set a pattern to run on startup (encrypted).
After I've rebooted the phone the pattern stopped working, the pattern kept working in TWRP.
Methods I've tried to resolve the issues:
- Tried to remove all lockscreen's related file according to the following ( https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008 ) .
- Cleaned flash another rom
- Cleaned flash a backed up rom
- Factory reset
- Updated to the latest blu spark recovery
- Tried flashing Cardinal Xtended
the result is the same - the rom does not accept any pattern, TWRP accepts all pattern, no files exists in /date/system
What am I missing here? this is the first time i'm running into this kind of bull****
EDIT: Seems like an hardware issue, the internal sdcard is totally not recognized after a format from fastboot
edit #2: got resolved, thanks.
Click to expand...
Click to collapse
How? Can you share your method so the next person knows what to do?
I ran into this problem and "fixed" it by goign back to Nougat
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
exocetdj said:
A lot of people rooted are having issues with DEX with either systemUI closing, systemuidex closing or the app only staying open on PC pr TV for a few seconds.
Please can anyone who is rooted please let me know if they can access DEX and if so - is it working for you?
Please show a pic of magisk front screen with version number and state your exact rooting procedure
Hopefully we can then find out what is breaking dex
UNLESS anyone knows what sort of log may diagnose the issue? I have a dumpstate/logcat but not sure what part im looking at
Click to expand...
Click to collapse
We're do I get root how to for the u version
The only version that is rooted is the B version. The international, European, and North American versions are not able to be rooted.
We have root on the B variant
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
lilplanet said:
I believe the issue is related to having the "Data" folder being decrypted - This "Decrypting" process is on step # 4 under the 2nd process "PROCESS IF COMING FROM STOCK A12"
I have tried the process without the "Formatting the data" step which allows me to boot with root + Dex working. The only issue is that I'm limited to storage, It's fixed to 32gb out of the original size(512gb). Is there a way to resolve the limited storage issue?
Note: If we decrypt the data(Format data via twrp), we are restricted to:
- Cannot share pics in Samsung Gallary
- Dex's system ui constantly crashes
- Cannot install apps such as games that requires external downloads from installing an apk
- GMail cannot download embed files from an email
- ETC anything related to storage within the data, we cannot access/delete/edit when the data is decrypted
Click to expand...
Click to collapse
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
exocetdj said:
Thats some great info thanks very much
although that would also effect the download and install of Magisk potentially and that works - do you have an example of an app or game doing this so i can test?
i can confirm i cannot share pics directly from gallery but can within apps such as telegram
Downloading docs from Gmail is buggered
Dex is RIP.
@ianmacd do you think there is something we could be missing - we are effectively doing the disabler's job manually on F926B and its not unreasonable to think we may have missed something - could running the multidisabler be useful to see if it picks something up (even if it completely breaks things) so that we can then do the required modification manually?
Click to expand...
Click to collapse
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
pvillasuso said:
Me again
BVA9 STOCKRooted !
No sharing issues , and 100% working DEX
I used your BL file , extracted recovery from your AP File to make an Odin flashable TWRP.tar to sideload and flash your app-debug.zip
Click to expand...
Click to collapse
whats your internal storage size? and have you reset device since you last managed to get this working?
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
pvillasuso said:
Yes , I have reseted the phone.
When flashing to stock I used CSC ( the one that wipes data )
Did a stock recovery factory reset and also format data when I used the twrp recovery .
There is something with wrong with your AP file Bro , because I first used that file , and I tried the camera and had the sharing issue . Same happened with your older build , So I think the problem is there.
I Have the 256gb version
Click to expand...
Click to collapse
Ok sounds promising
Please can you provide a step by step procedure here and if i can replicate it i will amend the first post and files in the rooting thread
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
exocetdj said:
looks like formatting in TWRP could be the issue then - and we need to format at a different stage? (please still provide full process)
Click to expand...
Click to collapse
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pvillasuso said:
Yes , do that factory reset from stock recovery .
I also think the twrp format is not working as expected
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this:
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
******
So I'm sure the BL file helped me to flash TWRP , because I tried it alone (TWRP) and it didn't work ( got bootloops ending in download mode ).
What I didn't try , now that Im reading myself , was to do a factory reset from stock , after doing that initial setup , and tried to flash that TWRP file right after that.
links to files :
AP_twrp_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
AP_stockrecovery_F926B_A12_BVA9
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
do you have stock recovery or TWRP installed now you have root?
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
Stock recovery now
I can try to flash twrp , and can go back to stock recovery if it doesnt work
exocetdj said:
do you have stock recovery or TWRP installed now you have root?
Click to expand...
Click to collapse
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
exocetdj said:
the key is that if you install TWRP now and dex and file sharing etc etc is still working then i need to look at these files
As far as im aware = the DEX issues are a result of having TWRP installed
Click to expand...
Click to collapse
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
pvillasuso said:
Well, then I can try to install twrp , and launch DEX to see how it goes
Be right back and let you know
edit :
Flashed TWRP successfully !
No sharing issues , Dex working fine !
Click to expand...
Click to collapse
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
exocetdj said:
ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc
so i am missing TWRP
please can you go into finer detail into what you then did to install TWRP i need to have as much information as possible - please also confirm if you can mount data and flash files in TWRP if not then there is not really much point in having TWRP installed - i am thinking this is unlikely as you have not disabled forcencryption
I have managed to follow this far
1. Flash odin to stock , NOT using HOME_CSC
2. Do the initial setup (usb debugging and OEM status ( if shown ) checked
3. Flash odin the BL file , and TWRP.tar
4. TWRP , format ( I think nothing happened in this step ), reboot to TWRP , sideload and flash app-debug.zip
5. Reboot to download mode and flash stock recovery , and do the factory reset there ( at this step I tought I woud lose the previously flashed magisk stuff , but that didnt happen, and I got booted & rooted )
I am now rooted with stock recovery - i find it hard to see how we can just install TWRP and use it normally and mount /data without having to at least destroy user data each boot as forcencrypt has NOT been disabled
what is making things far too hard is a process that follows things like this:
"
edit : about the full process...
I ended again in a mess , and did several random stuff (as I got stuck some times in Download mode)
But .. If you ask me what I think that works , it would be like this: "
there are just too many variables - for instance, forceencryption could have been disabled without you realizing when doing the random bits - did you reflash my AP files at any point?
Click to expand...
Click to collapse
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Edit : Nice that you could replicate it !
"ok so i am now rooted with stock recovery and everything is working - Dex, sharing etc etc "
pvillasuso said:
I agree with you about the variables
In short
I was rooted with stock BL6 and twrp
So I flashed to this newest stock , and tried to keep my setup and get rooted again
I flashed HOMECSC and after that gave a shot with newest twrp ( to flash newest app-debug.zip )
I ended with a download mode bootloop
So I used your guide with your files , everything went fine .. except for the sharing and dex issues
This is when the forceencryption could have been disabled , exactly !
Then , I did the steps above , back to 100% stock ( steps above ) , without your AP File this time .
TWRP , is useless at this point , it cant mount data , it is the same behaviour as with BL6 version
Click to expand...
Click to collapse
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
exocetdj said:
Thanks for the info
looks like using TWRP at a starting point is the only way thats going to be of any use - rooted stock is the way forward!!!
Click to expand...
Click to collapse
Sure Bro , no problem
I am using 6 pro and got a huge problem.
My P6 pro is in fresh status and proceed a new setup with a new Google a/c. No matter in safe mode or normal mode, it always get into recovery mode - "can't load android system". Below picture is the log I capture from recovery mode. Could anybody help me? Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Morgrain said:
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Click to expand...
Click to collapse
I did not root or install magdisk to the phone. I just openbox, turnon the phone, everything starts normal, do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
ecuchi said:
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
I did not root my device. Everything starts normal and i do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once the phone reboots, it goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Alekos said:
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Click to expand...
Click to collapse
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
RetroTech07 said:
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
Click to expand...
Click to collapse
No, I did not do any modification. I also try the pixel repair but no use.
jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
I have seen this Scenario hours ago when I try to disable vbmeta to get the corrupted message appearing after booting.
Because I disabled vbmeta flags, wiping is necessary, therefore I choose factory data reset. issue fixed, data lost. that's all
jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Alekos said:
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Click to expand...
Click to collapse
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
jozifkwan said:
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
Click to expand...
Click to collapse
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Alekos said:
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Click to expand...
Click to collapse
Thank you, I tried your guideline to flash, tick "wipe" and "flash all partitions", flash slot A first and then flash slot B.
The problem is still the same, once I finished the setup, reboot, goes into recovery again and said "cannot load android system"
Beginning to sound like you should exchange it for a new one, unfortunately.
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Sounds like a hardware issue with the NAND.
LLStarks said:
Sounds like a hardware issue with the NAND.
Click to expand...
Click to collapse
I believe it is not the NAMD.
Last night, I test the battery to see if the corruption issue is caused by unstable voltage or ampere. I run drain app + 3D mark, my phone of course heats up but no reboot or unstable issue.
The battery test drained 60% of battery and i manually reboot the phone, no problems or errors and enter system. Then I left the phone in stanby mode for 7 hours. The battery downs to 35% and I reboot the phone again but this time unfortunately goes into recovery issue again.
This is very weired and I couldn't figure out what kind of problem is that.
stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
I am wondering if anyway to skip the recovery or corrupt checking.
stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
you have the corrupt message also? Can you try what I recommended above, updating all 4 Play Services/Play Store Apps/Security Update and Play System Update with Bluetooth disabled?
If not use the Android Flash Tool and wipe the device and flash all slots, let us know if that works.