Hello you brilliant people! I haven't been on here in some time. I recently move to China and brought along my Galaxy S3 i-535. It's been some time since I've worked with flashing custom ROMs and never tried it on the S3 until I came here. I am able to root, unlock the boot loader, and install CWM. However, whenever I try and flash any ROM I get the ever infuriating (Status 7) assert. Meaning that I have the incorrect ROM, correct? But I have double, triple, and quadruple checked and I have the correct ROM. Here are the pertinent details:
=============================================================
-Samsung Galaxy S3 I-535
-Originally a Verizon phone (Screw VZW!)
-Currently on the ChinaMobile network with a Chinese SIM card
-CWM v6.0.2.3
-And I'm currently on Android 4.1.2
-Baseband Ver.: I535VRBMB1
-Kernal Ver.: 3.0.31-861013 (not sure if useful, but maybe)
=============================================================
Here is the my specific question. ##Could I be receiving the Status 7 assert due to the different SIM card/network??##
I've tried removing the assert from the updater-script file, but no luck. I changed almost a year ago, so the old SIM card is long lost and finding a VZW SIM here would be nearly impossible.
I believe my CWM version is new enough.
If this is the case, any suggestions on where to go next? Any developer/website that would work with China Mobile is in Chinese, and my Chinese is VERY poor.
I need to update my phone to receive data, so they say, but I'm not sure how high I have to update. I was trying to avoid 4.3 because of the locked bootloader. But I think I can find a ROM for 4.3 or 4.4 that doesn't force me to take the locked boot loader? Am I correct in my thinking. Yes I have been researching, I just want to make sure I'm right.
Any useful assistance will be rewarded with my endless gratitude and kind thoughts!!!
You want to upgrade your CWM to 6.0.4.5 then flash your roms from there. If you're using Rom Manager, you can upgrade from within the app itself. Alternatively, you can download the CWM 6.0.4.5 recovery IMG file from the official CWM website, download "Flashify" from the Play Store then install the CWM 6.0.4.5. recovery img file using Flashify.
WOot woot!!!!
SlimSnoopOS said:
You want to upgrade your CWM to 6.0.4.5 then flash your roms from there. If you're using Rom Manager, you can upgrade from within the app itself. Alternatively, you can download the CWM 6.0.4.5 recovery IMG file from the official CWM website, download "Flashify" from the Play Store then install the CWM 6.0.4.5. recovery img file using Flashify.
Click to expand...
Click to collapse
That was all it needed! Success! Running the latest Cyanogen!
Much thanks, much thanks!
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Sounds like you flashed the wrong recovery, possible that you installed the p3100 recovery.
Try reflashing the recovery.
miksol said:
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Click to expand...
Click to collapse
Flashing KK ROMs on outdated recovery will get you a status 7 error. Grab the latest (I'd go with TWRP as CWM support will be ending soon) version from here...http://forum.xda-developers.com/showthread.php?t=2548257 update to the latest one you like (CWM is 6.0.5.0) Load up a ROM and give it a go. I put all my ROMs on an external card to be safe. Maybe do that and then just install from such.
p,s. CM installer never works, I dont think our tabs are compatible with it. At least I've never got it to work.But, you dont need it anyways.
Just want to share an experience i went thru while trying to root my metro pcs galaxy s5 on android 5.1.1 I've read in a few forums that it cant be rooted. Or you had to downgrade firmware in order to root. I Was able to root & install TWRP recovery on my galaxy s5. Using Chainfires CF auto root for metro klte. And Odin v3.07 All while never fully booting ( stuck in boot loop) my phone.
1) powered phone to download mode.
2) connected to odin, flashed cf auto root. Phone passes unplug from computer.
3) phone boots up but stays on galaxy s5 boot screen.( never fully boots)
4) removed battery, put back, powered phone to stock recovery, factory reset it. Reboot, again. Still stuck on boot loop.
5) removed battery again, put back, powered phone to download mode, noticed knox counter was now tripped. 0x1, and phone status was now custom instead of official. Took a chance...
6) connected phone back to odin, flashed TWRP recovery img. Phone passes again, boots up but still stuck on galaxy s5 boot screen.
7) removed battery, put back once more, powered phone into recovery mode. To my surprise TWRP recovery now installed.
8) In twrp recovery did a full wipe, and flashed custom rom, and gapps. Now wife is enjoying her Cm 12.1 rom.
Was surprised to learn all this was accomplished without fully booting my phone ( sort of stuck in soft brick) and not verifying root with root checker app.
Sent from my SM-G900T using Tapatalk
Spelling, updates
Nemsiis72 said:
Just want to share an experience i went thru while trying to root my metro pcs galaxy s5 on android 5.1.1 I've read in a few forums that it cant be rooted. Or you had to downgrade firmware in order to root. I Was able to root & install TWRP recovery on my galaxy s5. Using Chainfires CF auto root for metro klte. And Odin v3.07 All while never fully booting ( stuck in boot loop) my phone.
1) Powered phone to download mode.
2) connected to odin, flashed cf auto root. Phone passes unplug from computer.
3) phone boots up but stays on galaxy s5 boot screen.( never fully boots)
4) removed battery, put back, powered phone to stock recovery, factory reset it. Reboot, again. Still stuck on boot loop.
5) removed battery again, put back, powered phone to download mode, noticed knox counter was now tripped. 0x1, and phone status was now custom instead of official. Took a chance...
6) connected phone back to odin, flashed TWRP recovery img. Phone passes again, boots up but still stuck on galaxy s5 boot screen.
7) removed battery, put back once more, powered phone into recovery mode. To my surprise TWRP recovery now installed.
8) In twrp recovery did a full wipe, and flashed custom rom, and gapps. Now wife is enjoying her Cm 12.1 rom.
Was surprised to learn all this was accomplished without fully booting my phone ( sort of stuck in soft brick) and not verifying root with root checker app.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
As long as odin says "success"!! Then you should be golden.
In fact your success might also be attributed to the boot loop not being able to auto-wipe and restore the factory recovery before TWRP had a Chance to take hold.
No doubt that TWRP contributed to the success of CF-autoroot for this device & 5.1.1 software combination.
Heres My story...
I too have the metro pcs galaxy s5 on android 5.1.1... All be it.. it's 5.1.1 now because of an OTA firmware update that T-Mobile released. I downloaded it because I intended to root the stock 5.1.1 android image..
( and that is what I achieved, two S5's fully rooted on stock 5.1.1 image, with custom recovery, and customized and de-bloated to my liking)...
I was previously rooted on 4.4.2 with this S5, So I flashed the stock T-Mobile firmware I got from samfirwares.com using Odin3 v3.10.6 to esentaly unroot and get stock 5.1.1.
My device having already been rooted before on 4.4.2, would not alow me to OTA to the 5.1.1 update that Metro PCS pushed via the network.... (My wife's non-rooted S5 however; was able to receive it via the network so I rooted hers the same way as mine following same steps minus flashing the stock firmware with odin after first using mine as the guinea pig.)
That said.. After first reboot of stock 5.1.1. Firmware I verified my fears and indeed root had been broken.
I then immediately returned to download mode and flashed TWRP via Odin, after reboot I then immediately booted to TWRP recovery and flashed the waiting CF-autoroot.zip I had placed on SD previously while on 4.4.2. .... So.. root was easily achieved
Thanks to TWRP..
If I remember correctly I did have the same need to pull the battery after flashing TWRP via odin.. due to hanging on the Samsung logo....
To sum this up:
1. I'M ON STOCK 5.1.1 WITH TWRP AND ROOT ON MY S5.
2. Knox is not tripped, (update its now tripped thanks to Titanium Backup... useless app in my opinion now that others can freeze/disable system apps. )
3. Because of the way that all of my flashing went without issue.. I never lost contacts, homescreen background, icon & widget layout, or settings. (I DID HAVE TO RE-ENABLE Developer Mode and USB debugging along with animation settings, also had to run "SD fix" again one time, but that's it.) I DIDN'T EVEN HAVE TO put my WiFi passwords back.
Ps I know most of that can be backed up and restored automatically. But I never had to bother.
NOTE: After each step following the successful flash of TWRP do yourself a favor and make a Nandroid backup to the SD. (U'll need at least 32gb to make 3 full incremental backups and still have space.) I suggest transferring them to USB or PC ASAP so that if u some how wipe the SD card U'll still have a way back.
I liked CM10 on my old phone... maybe now that I've made my nandroid backups at each step along the way I have little to loose if I try a custom S5 rom now..
Anybody have any ROM suggestions, they have personally flashed on S5?
Closing thoughts:
I full owe all of my success to the wonderful community of developers here on XDA-developer forums..
Without them and their strong following of loyal users, I would never have even attempted this on my S5.
Nor would I have been able to root my wife's unrooted android 5.1.1 MetroPCS Samsung Galaxy S5.
XDA has now helped me accomplish root on more then 10 devices over the years..
Thank you XDA, & a special thanks to Chainfire, Team Win Recovery Project, Clock Work MOD (for their help with previous devices), and all the testers out there.
THANK YOU ALL..
Sent from my SM-G900T using XDA Free mobile app
Im running this Rom at the moment. XDA dev. Albinoman's unofficial Cm 12.1 along with the suggested gapps and it runs flawlessly on my metro pcs galaxy s5. Haven't had an issue yet. You will find it in the xda forum under galaxy s5 unified development sub forum.
So far I've ran 6 custom ROMs on my galaxy, and this one seems the best so far.
Your rooting process was interesting, effective but interesting!
It's cool finding out new was this thing can be achieved.
Have fun bro.
STAY ROOTED....
TEFjLONjDON said:
As long as odin says "success"!! Then you should be golden.
In fact your success might also be attributed to the boot loop not being able to auto-wipe and restore the factory recovery before TWRP had a Chance to take hold.
No doubt that TWRP contributed to the success of CF-autoroot for this device & 5.1.1 software combination.
Heres My story...
I too have the metro pcs galaxy s5 on android 5.1.1... All be it.. it's 5.1.1 now because of an OTA firmware update that T-Mobile released. I downloaded it because I intended to root the stock 5.1.1 android image..
( and that is what I achieved, two S5's fully rooted on stock 5.1.1 image, with custom recovery, and customized and de-bloated to my liking)...
I was previously rooted on 4.4.2 with this S5, So I flashed the stock T-Mobile firmware I got from samfirwares.com using Odin3 v3.10.6 to esentaly unroot and get stock 5.1.1.
My device having already been rooted before on 4.4.2, would not alow me to OTA to the 5.1.1 update that Metro PCS pushed via the network.... (My wife's non-rooted S5 however; was able to receive it via the network so I rooted hers the same way as mine following same steps minus flashing the stock firmware with odin after first using mine as the guinea pig.)
That said.. After first reboot of stock 5.1.1. Firmware I verified my fears and indeed root had been broken.
I then immediately returned to download mode and flashed TWRP via Odin, after reboot I then immediately booted to TWRP recovery and flashed the waiting CF-autoroot.zip I had placed on SD previously while on 4.4.2. .... So.. root was easily achieved
Thanks to TWRP..
If I remember correctly I did have the same need to pull the battery after flashing TWRP via odin.. due to hanging on the Samsung logo....
To sum this up:
1. I'M ON STOCK 5.1.1 WITH TWRP AND ROOT ON MY S5.
2. Knox is not tripped, (update its now tripped thanks to Titanium Backup... useless app in my opinion now that others can freeze/disable system apps. )
3. Because of the way that all of my flashing went without issue.. I never lost contacts, homescreen background, icon & widget layout, or settings. (I DID HAVE TO RE-ENABLE Developer Mode and USB debugging along with animation settings, also had to run "SD fix" again one time, but that's it.) I DIDN'T EVEN HAVE TO put my WiFi passwords back.
Ps I know most of that can be backed up and restored automatically. But I never had to bother.
NOTE: After each step following the successful flash of TWRP do yourself a favor and make a Nandroid backup to the SD. (U'll need at least 32gb to make 3 full incremental backups and still have space.) I suggest transferring them to USB or PC ASAP so that if u some how wipe the SD card U'll still have a way back.
I liked CM10 on my old phone... maybe now that I've made my nandroid backups at each step along the way I have little to loose if I try a custom S5 rom now..
Anybody have any ROM suggestions, they have personally flashed on S5?
Closing thoughts:
I full owe all of my success to the wonderful community of developers here on XDA-developer forums..
Without them and their strong following of loyal users, I would never have even attempted this on my S5.
Nor would I have been able to root my wife's unrooted android 5.1.1 MetroPCS Samsung Galaxy S5.
XDA has now helped me accomplish root on more then 10 devices over the years..
Thank you XDA, & a special thanks to Chainfire, Team Win Recovery Project, Clock Work MOD (for their help with previous devices), and all the testers out there.
THANK YOU ALL..
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my SM-G900T using Tapatalk
I was hoping for a root for the stock rom, has anyone found a method to root stock rom yet?
Another method FYI
Nemsiis72 said:
Just want to share an experience i went thru while trying to root my metro pcs galaxy s5 on android 5.1.1 I've read in a few forums that it cant be rooted. Or you had to downgrade firmware in order to root. I Was able to root & install TWRP recovery on my galaxy s5. Using Chainfires CF auto root for metro klte. And Odin v3.07 All while never fully booting ( stuck in boot loop) my phone.
1) powered phone to download mode.
2) connected to odin, flashed cf auto root. Phone passes unplug from computer.
3) phone boots up but stays on galaxy s5 boot screen.( never fully boots)
4) removed battery, put back, powered phone to stock recovery, factory reset it. Reboot, again. Still stuck on boot loop.
5) removed battery again, put back, powered phone to download mode, noticed knox counter was now tripped. 0x1, and phone status was now custom instead of official. Took a chance...
6) connected phone back to odin, flashed TWRP recovery img. Phone passes again, boots up but still stuck on galaxy s5 boot screen.
7) removed battery, put back once more, powered phone into recovery mode. To my surprise TWRP recovery now installed.
8) In twrp recovery did a full wipe, and flashed custom rom, and gapps. Now wife is enjoying her Cm 12.1 rom.
Was surprised to learn all this was accomplished without fully booting my phone ( sort of stuck in soft brick) and not verifying root with root checker app.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Here is what I did to achieve root on my MetroPcs galaxy s5 on lollipop: I headed over to: http://www.sammobile.com/firmwares/database/SM-G900T/ and downloaded the newest FOJ4 firmware for the T-MOBILE VERSION of the s5. I flashed this through Odin. Then I went to: https://twrp.me/devices/samsunggalaxys5qualcomm.html and downloaded the Odin flashable version of TWRP. I flashed this through Odin. Then I headed here: http://xda-android-foru.blogspot.com/2015/11/rootkernel-root-method-for-foj4.html?m=1 and downloaded the version you can flash through TWRP. Move that file to your SD card on your phone and then reboot to recovery and flash that zip file. Boom you have now achieved root on your MetroPcs galaxy s5 on lollipop 5.1.1 albeit you now basically have a t mobile phone. Next thing you can do is just change your apn settings to those that MetroPcs uses to get your data and mms working properly. Just Google "MetroPcs apn settings galaxy s5" and follow the instructions on those sites that pop up. Hope this helps. I got tired of waiting for a release of a dedicated root method for the MetroPCS Galaxy s5, but there are plenty available for the T-MOBILE variant.
MotorBoater84 said:
Here is what I did to achieve root on my MetroPcs galaxy s5 on lollipop: I headed over to: LINK1 and downloaded the newest FOJ4 firmware for the T-MOBILE VERSION of the s5. I flashed this through Odin. Then I went to: Link2 and downloaded the Odin flashable version of TWRP. I flashed this through Odin. Then I headed here: "This Link" and downloaded the version you can flash through TWRP. Move that file to your SD card on your phone and then reboot to recovery and flash that zip file. Boom you have now achieved root on your MetroPcs galaxy s5 on lollipop 5.1.1 albeit you now basically have a t mobile phone. Next thing you can do is just change your apn settings to those that MetroPcs uses to get your data and mms working properly. Just Google "MetroPcs apn settings galaxy s5" and follow the instructions on those sites that pop up. Hope this helps. I got tired of waiting for a release of a dedicated root method for the MetroPCS Galaxy s5, but there are plenty available for the T-MOBILE variant.
Click to expand...
Click to collapse
The third link is down buddy. Can you update it please.
Hi all,
I have an Galaxy Note Edge type SM-N915FY with custom rom installed: http://forum.xda-developers.com/note-edge/development/rom-micky387-rom-v1-0-t2998972
My phone is running on android 5.0.1 with kernel: 3.10.30-andrei-N915F-BOC6-v1.0
Baseband-version: N915FYXXU1BOB5
Yesterday I was trying to install the newer custom rom: http://forum.xda-developers.com/note-edge/development/rom-micky387lollifamous5-1-1v1-t3200849
To make sure this will work, I needed to flash the TWRP , after I tried to flashed this using Odin, the phone got in a Bootloop. So I flashed the older TWRP again and my phone is booting again.
So I tried to clear the cache, but then I get the error: Unable to mount \cache, I didn't know how to solve this so I reflashed the TWRP again through Odin, but still the same issue.
Do you guys know how I could install another custom rom? My phone is rooter, just to make sure.
Thanks in advance.
nobody?
notneeded said:
nobody?
Click to expand...
Click to collapse
To move on to newer custom ROMs (based on 5.1.1), you need to download and flash Stock 5.1.1, which you can download from here, then you can root it, to get the necessary files for doing so, check this thread out.
Credits for TWRP, new ROMs and the possibility of root on 5.1.1 go to micky387.
You Saved me. After I flashed the original android 5.1.1 I was able to flash TWRP and install custom rom.
Many thanks!
Hello,
I have got a problem to do anything with my tablet N8010. Some time ago I flashed custom ROM Lineage 14.1 (android 7.1) using custom recovery TWRP. Everything works fine except on some bugs in the ROM. These bugs convinced me to flash good old stock Kitkat ROM. But there is a problem. My USB port is somehow broken - I bless god that it charge battery at least but data communication is dead even when using different accessories. Problem is even worse because I managed to flash stock recovery over TWRP. If I recapitulate this, I cannot flash stock ROM over odin because USB data transfer does not work. I am stuck with stock recovery which allow me to flash only Samsung signed ZIPs.
The target is to either root Lineage ROM or get back custom recovery somehow.
What i have tried already:
LineageOS - addonsu-arm-signed.zip
This ZIP should be flashed through custom recovery to achieve ROOT access but thanks it is unusable unfortunately thanks of absence of Samsung's signature
All kind of ONE-CLICK-ROOT-APPS
Since i cannot root device through USB cable I have to use applications to try to reach root state. I have tried most common apps for this kind of purpose but non of these worked.
Ideas to solve this kind of problem
ADB-ROOT option in LineageOS
I can enable ADB-ROOT access in developers settings. I know there is a way of connecting to ADB via Wi-Fi. This I have tried already and I was successful.
Questions:
Will the Wi-Fi connection persist event when going to bootloader?
Is it possible to flash custom recovery at least from booted Android through ADB?
Is there any other way to flash or root recovery not from bootloader?
Use stock TAR.MD5 file
I managed to get all IMG files from stock firmware .md5 file but is it useful somehow? Can i just put them into ZIP archive and flash it through stock recovery or ADB-ROOT?
Prepare ZIP for stock RECOVERY
I would either need custom recovery ZIP (not IMG or tAR.MD5 file) to flash it through stock recovery or create / change / delete some attributes in ZIP file to be able to pass the signature verification of stock RECOVERY
This is my situation. External SD and Wi-Fi are only friend of mine in this situation and I am asking you kindly if I am stuck with ROM I have or if I have a chance to resolve the issue and flash stock ROM.
Thank you
Have a look and see if Mobile Odin or Flashfire work on this tablet .
JJEgan said:
Have a look and see if Mobile Odin or Flashfire work on this tablet .
Click to expand...
Click to collapse
Mobile odin works but i do not have rooted devive
Flash supersu zip .
JJEgan said:
Flash supersu zip .
Click to expand...
Click to collapse
Since i am stucked with stock recovery, the signature verifying fails. I does not work.
I have managed situation by following this article. Also, do not forget to type adb root before typing adb shell
https://blog.zauberstuhl.de/flash-your-recovery-image-via-adb-shell-on-android/