Related
Hello All,
I have been using Illusion 4.2.2 and want to go to 4.3.
I have been facing the following issues -
1) After upgrading to the latest cwm (6.0.3.8), I tried flashing PA 4.3. With a clean wipe and format system, it gave me a status 7 error (installation aborted).
One of XDA members redirected me to this - http://forum.xda-developers.com/showthread.php?t=2321310. I followed this and following is the screenshot of what I have after upgrading the bootloader : (Below jpg which says "Just after upgrading bootloader)
2) I could now flash the rom but when I rebooted after flashing , I don't have root access and neither do I see any att network / data . Following are the screenshots -
(Just after flashing 4.3 Page 1/2 and No root access after flashing 4.3).
ND
_ND_ said:
Hello All,
I have been using Illusion 4.2.2 and want to go to 4.3.
I have been facing the following issues -
1) After upgrading to the latest cwm (6.0.3.8), I tried flashing PA 4.3. With a clean wipe and format system, it gave me a status 7 error (installation aborted).
One of XDA members redirected me to this - http://forum.xda-developers.com/showthread.php?t=2321310. I followed this and following is the screenshot of what I have after upgrading the bootloader : (Below jpg which says "Just after upgrading bootloader)
2) I could now flash the rom but when I rebooted after flashing , I don't have root access and neither do I see any att network / data . Following are the screenshots -
(Just after flashing 4.3 Page 1/2 and No root access after flashing 4.3).
ND
Click to expand...
Click to collapse
Some roms you have to turn on root access; should be in the install post. Are you running the right rom for your device?
thepoetlives89 said:
Some roms you have to turn on root access; should be in the install post. Are you running the right rom for your device?
Click to expand...
Click to collapse
I eliminated that possibility because the same thing happened with two different roms (PA 4.3 and Illusion 4.3). I am on ATT and this phone is a ATT phone , and I am flashing all roms within this thread
_ND_ said:
I eliminated that possibility because the same thing happened with two different roms (PA 4.3 and Illusion 4.3). I am on ATT and this phone is a ATT phone , and I am flashing all roms within this thread
Click to expand...
Click to collapse
I know with illusion you have to ::Settings -> Developer options -> Root access to apps and/or adb. to get root access. Where are you getting basebands from? The latest is I747UCDMG2 but I747UCDLK3 should work too. Get them from HERE
thepoetlives89 said:
I know with illusion you have to ::Settings -> Developer options -> Root access to apps and/or adb. to get root access. Where are you getting basebands from? The latest is I747UCDMG2 but I747UCDLK3 should work too. Get them from HERE
Click to expand...
Click to collapse
I flashed the Illusion 4.3 again and then flashed baseband using the this link (through ODIN).. I still see an unknown baseband in the about and no mobile network (image attached)
The root access got sorted out , thought. thank you !
_ND_ said:
I flashed the Illusion 4.3 again and then flashed baseband using the this link (through ODIN).. I still see an unknown baseband in the about and no mobile network (image attached)
The root access got sorted out , thought. thank you !
Click to expand...
Click to collapse
some more research told me that I have lost my imei number. I remember taking a backup of my efs folder the first time I rooted my phone a year back. Can anyone help me restore my network using that backed up folder ?
_ND_ said:
I flashed the Illusion 4.3 again and then flashed baseband using the this link (through ODIN).. I still see an unknown baseband in the about and no mobile network (image attached)
The root access got sorted out , thought. thank you !
Click to expand...
Click to collapse
Baseband is Here. I would suggest MG2 baseband as it is more compatible with 4.3 than older than LK3. Get it from the link i just gave you and follow instructions on the page. Only use odin for reverting back to STOCK.
thepoetlives89 said:
Baseband is Here. I would suggest MG2 baseband as it is more compatible with 4.3 than older than LK3. Get it from the link i just gave you. ^^ and flash through recovery. Only use odin for reverting back to STOCK.
Click to expand...
Click to collapse
I tried the MG2 but the baseband still shows up as Unknown in About
_ND_ said:
I tried the MG2 but the baseband still shows up as Unknown in About
Click to expand...
Click to collapse
Huh thats weird. The only thing i can think of is something is wrong with the rom or you are flashing a non d2att rom.
thepoetlives89 said:
Huh thats weird. The only thing i can think of is something is wrong with the rom or you are flashing a non d2att rom.
Click to expand...
Click to collapse
I suspected that but since a lot of people are already using that rom and I made sure I am downloading d2att , those things are eliminated.
I am thinking the 4.3 flashing erased my previous efs folder and that is why it cannot find my imei number anymore - resulting in no network.
_ND_ said:
I suspected that but since a lot of people are already using that rom and I made sure I am downloading d2att , those things are eliminated.
I am thinking the 4.3 flashing erased my previous efs folder and that is why it cannot find my imei number anymore - resulting in no network.
Click to expand...
Click to collapse
When you get imei back i would suggest a nvbackup to make sure you keep a good backup of your imei.
thepoetlives89 said:
When you get imei back i would suggest a nvbackup to make sure you keep a good backup of your imei.
Click to expand...
Click to collapse
I had a nvbackup but since I flashed a different of baseband , I was not able to recover.
Anyways, I flashed stock through odin and looks like I have my network back.
Any recommendation of which 4.3 rom will not cause this again ? Anyone ?
try updating roms from ics up to 4.3and update modem and bootloader.
Hi,
I am just writing these steps to help those who want to downgrade from KK to JB due to any reason. Please use these steps at your own risk.
Some Background:
Recently I updated my Razr M to KK, it was Locked and Unrooted, but with the help of Twelroot and Motopocalypse I rooted and unlocked the BL.
Now somehow I didn't like the KK and wanted to go back to JB 4.1.2 because I was now having unlocked BL and rooted phone so it was easy but need to follow some steps to successfully downgrade to JB. So an unlocked BL and rooted with KK is must.
Prerequisite:
USB drivers for Razr M must be installed before proceeding.
Steps:
1. download the firmware file [Android 4.1.2
Blur_Version.98.30.1.XT907.Verizon.en.US] from http://sbf.droid-developers.org/phone.php?device=8
2. extract the above archive and replace the XML file with the one in attachment.
3. put the phone into fastboot mode and flash the firmware with RSD Lite (attached)
4. reboot and now you have JB 4.1.2
If you want to install root application again and also want to flash custom recovery then please follow the Post#5 [ATTACK] (thanks ATTACK)
Note : for custom recovery you will need the fastboot.exe if you don't have it then install minimal_adb_fastboot_v1.1.3_setup.exe(attached).
Put the phone in fastboot mode, copy the recovery to c:\ and execute the below command :
fastboot flash recovery [Path to recovery image]
If it help you then don't forget to press Thanks button !
Forgive my ignorance but this won't downgrade the kernel will it? I'm hoping it's possible to go from the newest OTA to the stable CM11 but I'm guessing this is new kernel JB. Either way thanks if I can't go to stable CM11 I'll stick with rooted 4.1.2.
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
ATTACK said:
Once you have a unlocked bootloader, you do not need to use "root programs". All you need to do is flash a custom recovery via Mfastboot / fastboot then flash SuperSU / Superuser.
In dhacker29's folder there are 2 different recoveries.
"msm8960" is for 4.1.2
"KITKAT" is for 4.4.2
Click to expand...
Click to collapse
thanks ATTACK, can you please point out that which recovery is specially for 4.1.2 because there are a lot of recoveries with msm8960 in Dhacker29's folder.
One more thing if you have flashable Su and busybox zip then please attach it , i will update the OP.
thanks alot.
DHACKER29's FOLDER
- LINK
JELLYBEAN 4.1.2 RECOVERIES
- CWM-6.0.4.6-swipe-moto_msm8960
- TWRP-2.7.0.0-moto_msm8960-hdpi
KITKAT 4.4.2 RECOVERIES
- CWM6049-RAZR-HD_M-KITKAT
- TWRP2710-RAZR_M-KITKAT
SUPERUSER - I'm just going to link to Chainfire's thread, Direct people to download from there.
http://forum.xda-developers.com/showthread.php?t=1538053
BUSYBOX
https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
TheForceUnleashed said:
Could you go back to KK when you've downgraded to JB? Just asking this question early before the CM11 M8 release and the transition occurs.
Click to expand...
Click to collapse
Yes.
ATTACK said:
Yes.
Click to expand...
Click to collapse
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
TheForceUnleashed said:
So just by flashing the KK firmware in RSD without any changes to the xml? Sorry for the noob questions, I realize how easy this phone can be bricked and I want to avoid it.
Click to expand...
Click to collapse
I see don't why you would need to. It would be just like restoring stock firmware via RSD Lite.
When I try to flash this, I get Failure on 2/20, sbl1
jrk190 said:
When I try to flash this, I get Failure on 2/20, sbl1
Click to expand...
Click to collapse
Did you replace the XML file included in attachment?
Sent from my ME173X using Tapatalk
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
reply
is this sure it works? i read the feedback so,me user try it failed?
jrk190 said:
Sure did. I can't even restore to 4.4.2, I'm stuck on a broken system with no wifi or signal. This sucks...
Click to expand...
Click to collapse
Can you please post the error that is displayed in RSD Lite ?
The steps are tested by my 2 times, and there shouldn't be any problem. Make sure you have installed the correct drivers.
Please ensure that your bootloader is unlocked and shows BL unlocked status code 3 on BL screen.
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
xKroniK13x said:
I was also able to successfully flash back to JB with House of Moto via fast boot and full data wipe. It would not work with Universal or Keep Data, had to do full data wipe. Just another alternative :good:
Click to expand...
Click to collapse
I have used my method two time successfully, just follow the steps described in OP.
reply
Thanks You Its a Success Downgrade From 4.4 stock > CM11 > Stock rom 4.1 Thank you so much !!!
For those undergoing the downgrade process in RSD Lite and it takes forever for it to finish and the system ends up without data/signal, you need to RSD Lite flash again in order to regain signal. I believe the flashing was sluggish due to the jump from 4.4.2 to 4.1.2 and the many changes that were reflashed.
Sent from my DROID RAZR M using XDA Free mobile app
We have a wiener!
Thank you so much for the guide. After a lot of trial and error (mostly error), I thought that I had bricked my lovely XT907. I finally restored KitKat by flashing the 4.4.2 firmware with the edited XML file (deleting lines with "Getvar", "var" and "oem" in them), then followed your guide to the letter and found myself with a perfectly functional phone once again. No more sticky fastboot loops or audio-related crashes for me!
Lovely guide - thanks again! :laugh:
---------- Post added at 11:05 PM ---------- Previous post was at 10:59 PM ----------
What functionality does Busybox add? The description on the Play page is woefully sparse.
Thanks!
ATTACK said:
I *DON'T see why you would need to. It would be just like restoring stock firmware via RSD Lite.
Click to expand...
Click to collapse
*EDIT
I don't know why this posted as a new reply
I've flashed latest modem using TWRP and then flashed ROM Unofficial Cyanogenmod 12.1 and gapps.
Since then i lost IMEI,baseband etc, I can't even connect on WIFI.
I did save a copy of efs folder on my sd card and I backed up previous 4.4.2 android. I have restored old system and I flashed several older modems from list in forums (for my i747M) and i copied efs folder from sd card to root, but still no IMEI.
I did tried EFS Profesional but it wont start, says ADB server error.
Any ideas how to solve this? thanks
mls.ivanovic said:
I've flashed latest modem using TWRP and then flashed ROM Unofficial Cyanogenmod 12.1 and gapps.
Since then i lost IMEI,baseband etc, I can't even connect on WIFI.
I did save a copy of efs folder on my sd card and I backed up previous 4.4.2 android. I have restored old system and I flashed several older modems from list in forums (for my i747M) and i copied efs folder from sd card to root, but still no IMEI.
I did tried EFS Profesional but it wont start, says ADB server error.
Any ideas how to solve this? thanks
Click to expand...
Click to collapse
any luck mate? I'm in the same boat as you but I have wifi still. Commenting to follow or maybe you have a solution.
Did you flash the bootloader too? It is recommended that the bootloader and modem match.
audit13 said:
Did you flash the bootloader too? It is recommended that the bootloader and modem match.
Click to expand...
Click to collapse
No, I only did the modem. Should I do the 10.2 install or install modem + bootloader back to back?
fausto412 said:
No, I only did the modem. Should I do the 10.2 install or install modem + bootloader back to back?
Click to expand...
Click to collapse
Just install cm10.2 for now. If you only flash the mjb modem, you should be okay as I recall seeing that the phone already had the mjb bootloader.
Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.
rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.
ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?
Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !
Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help
I have spent the past 2 days trying to get a new cfw installed on my phone that didnt have many bugs. I settled with the cyanogenmod13 and read that it was good for a daily driver. At first i installed the wrong gapps and would make the keyboard crash, but now that i figured that out i need help with getting the rom to recognize the sim card. I tryed reflashing with twrp 2.8.6.0 because i read that it would flash the modem correctly, but still no luck. i'm fairly new to flashing and have only done it 3 times in the past. So now i made an account here to ask for help.
Thanks in advance to all the help i get here.
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
audit13 said:
Is the phone running the latest bootloader and modem? You can compare the versions in the phone to sammobile.com.
Click to expand...
Click to collapse
Thanks for your rely, Im not 100% sure what you mean by modem as im fairly new to this whole business. I will go to the website to see what i can find. Where can i see that information about the modem i am currently running?
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
audit13 said:
I recommend matching the bootloader and modem version to each other.
You can download the Samsung Phone Info app from the Play Store to learn about the phone.
Click to expand...
Click to collapse
Ok I did some research and learned that the modem is the baseband number that shows in the about phone section. This is currently unknown or my guess non existant and that is why the phone says that the sim card is not inserted.
I also learned that i can use ODIN to flash the modem/baseband directly without the need to reflash the whole rom.
I dont know where to find the file online for the modem that matches the rom. I have spent a while looking around and have seen older posts of people saying that they have experienced the same issues after flashing cm13 on n9005 Note 3.
Here is what i am running on my phone:
- Cyanogenmod Version: 13-20151031-UNOFFICIAL-hlte (maybe there is a newer version to this somewhere that has this issue fixed)
- Baseband: Unknown
- Kernal Version: [email protected] #5
- Build Number: 1
-hlte-userdebug 6.0 MRA58K 2127f69904 test-keys
What do you think? And thanks for you help so far. :good:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Wouldnt I be able to flash the modem with odin as long as it matches the phone model? or will that cause problems?
Good luck. I hope it works for your phone.
audit13 said:
The simplesting may be this: update TWRP to the latest version. You can flash the img file from TWRP.
Once TWRP has been updated, create a nandroid backup of the existing ROM.
Download the latest ROM from sammobile.com and flash the whole ROM. This is the simplest and safest option IMHO.
After flashing the stock ROM and making sure the sim is recognized and IMEI is correct, use Odin to flash the latest tar version of TWRP , boot into TWRP, restore backup, test your sim.
Click to expand...
Click to collapse
Tempestelf2 said:
Ok I will give it a go and let you know what Happens, it will take a while because Here in Ecuador i Have very slow internet. I have to leave the files downloading over night.
Thanks for you help
Click to expand...
Click to collapse
Updating to the latest version of TWRP is a bad idea. If you update to version 3.0+ you can't install ROM's that use the AROMA installer. The newer versions of TWRP do not support it. The best version I've found is 2.7.8.0 to be able to handle any flashing.
The biggest problem is the sim card in my opinion.
audit13 said:
The biggest problem is the sim card in my opinion.
Click to expand...
Click to collapse
The sim card works fine in Ecuador, I have used it before flashing to cm13. I found the website of the ones who made the build and noticed that the version that I have downloaded is 1.33 from Oct 31, 2015 and that their latest updates on the channel log is version 12. I will download and flash latest build and she if the issue is fixed.
I was referring to the card bot being recognized in CM, not on a stock ROM. Thanks.