Related
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Improper recovery.
samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:
samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy
Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers
Thanks for the guidance.
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.
Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3
antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.
oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes
FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!
Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any official KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it will brick the device!
How to unbrick: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040 (Credit goes to @tirta.agung)
OTA downloaded.... Now going with flashboot...
Need Some Help
Deleted
anyone flashed it yet???
Sent from my AO5510 using Tapatalk
Flashed it..initial boot will take a long time
blackyz said:
OTA downloaded.... Now going with flashboot...
Click to expand...
Click to collapse
I tried fastboot method now my phone is not booting
anyone done it successfully? my DL is halfway so I need procedural help.
Phone not booting
sharan.nyn said:
I tried fastboot method now my phone is not booting
Click to expand...
Click to collapse
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.
I flashed it with TWRP.
Awsm CM12S.
Super smooth !
mralam92 said:
I flashed with fastboot process successful but my phone not booting, nothing happening. i don't know what to do now no logo just dead.
Click to expand...
Click to collapse
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
sharan.nyn said:
Same here bro!
now following this
http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
Click to expand...
Click to collapse
service centre help or not?
Posted cm12
Just installed the zip version of cm12 on yu. Could not wait for the official ota update. Updated zip using cwm recovery which I had installed while the phone was running on the cm11 kitkat 4.4.4 version.
I understand that since this is just a system update there is no need to change or revert back to the original recovery.
(just a doubt- is it necessary to revert back to original 4.4.4 system stock recovery in case we get the OTA or the OTA will take care of any Custom recovery and will install iteslf?)
Initial boot will take a long time due to the Android Runtime (ART) virtual machine which is the improvisation over the Dalvik Cache. So please be patient for all the 122 apps to get registered in by ART. I had tried the ART while on cm11 4.4.4 (despite of system warning that it might lead to crashes etc... ), even then it took a very long time......
Working absolutely fine. Initial experience is awesome. Will be observing it now for some time. Most other features are similar to the cm11. no more 3g detection errors. Got to explore more....
My first posting in XDA.
I owe a lot to this community from which I have taken a lot. I hope I will be able to give back even little that I have got to help others. :good::good:
By zip version i mean the version that can be installed using the phone recovery with out the need of a computer to push the system (i.e. the flashable version). I am not aware what the debuggable version means.
mralam92 said:
service centre help or not?
Click to expand...
Click to collapse
Service center said they will pickup the device in 7-8 days
please tell me difference between OTA,Fastboot flashable image and Boot Debuggable image.And which one should I download to install.?
Titokhan said:
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Click to expand...
Click to collapse
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?
CM 12 update
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
dont flash thru fastboot all who flashed it thru are having hard bricked devices
weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
YES YOU CAN JUST FOLLOW THIS STEPS
1. Download official CM12s Ota(1st zip in the link).
2. Place the downloaded zip file in the ‘download’ folder on phone’s internal storage.
3. Boot Yureka into Stock Cyanogen recovery - To do so, power off the phone. Then press Volume Up + Volume Down and Power button simultaneously,Onec you boot into recovery do data/ factory reset.
4. Select ‘Apply Update’ > ‘choose from internal storage’ > /0 > Download > and select “cm-12.0-YNG1TAS0W0-tomato-signed.zip” file. The ROM will be flashed and you should be seeing the Android Bot
5. Once installation is over, go to main page and ‘wipe cache partition’
6. Then select Reboot system now
That’s it! Wait for a while as the device boots for the first time with all new and fresh Cyanogen OS 12.
IF you dont get anyhting just revert me back ,or pm will help you.:laugh:
Titokhan said:
Current firmware: Android 5.0.2, Build LRX22G, Cyanogen OS version 12.0-YNG1TAS0W0
OTA: http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
Fastboot flashable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Boot Debuggable image: http://builds.cyngn.com/cyanogen-os...cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
Use OTA for manually update from any KitKat build; don't use fastboot flashable images on existing devices with KitKat bootloader - it'll brick the device!
Click to expand...
Click to collapse
It just got updated if you flash it on kitkat bootloader, the device will get bricked
Many users have got their device bricked, the warning was too late I flashed it today at 1:50 AM
weshall said:
guys plzzz help me as lollipop is out for yu...can i install ?? i have rooted my yu but i m still on stock rom i.e cm 11 and i have cwm ,can i flash the cm12 zip file using cwm ..
Click to expand...
Click to collapse
Hi, You can very well install the .....signed.zip using the CWM recovery as I did.
1. Install the .....signed.zip file and not the ....flashable.zip or the ....bootable.zip files. Only the .....SIGNED.ZIP file either on your phone memory or sdcard
2. Reboot into the recovery mode either by using the advanced reboot option or by pressing the volumeup+down button and power buttons simultaneously and releasing them once you see the Yu logo and phone vibrates.
2. Use the Factory reset command first and then wipe the Cache
3. Navigate to the Install zip and chose the .....SIGNED.zip from either your phone memory or the SD Card as CWM has the option to chose the zip file. and swipe to install it.
4. After successful installation navigate to reboot and swipe to allow the system to restart.
5. Intial boot takes a very long time saying Android is updating. This is because Lollipop uses Android Runtime (ART) by default and not Dalvik Cache as a virtual machine for all apps. So please be patient till all the 122 or so apks are updated by ART. Takes around 10-15minutes.
6. The usual fist time boot stuff.... and then...
7. Enjoy. CM12 it is sweet.
---------- Post added at 09:58 AM ---------- Previous post was at 09:43 AM ----------
id74em8 said:
Is the Android version 5.0.x or 5.1?
Has anyone encountered any bugs at all?
To flash through recovery, do I need the OTA version?
Click to expand...
Click to collapse
It is android version 5.0.2
To flash through recovery (either CWM or TWRP) use the .....SIGNED.ZIP i.e. the first file in the list and NOT the .flashable.zip or the last one. Only the first one.
I installed the zip through CWM
The only bug I noticed was when you add the Powersaver option tile in the Notification drawer, when in the power saving mode, a notification showing the power save mode got invoked. When I used the same option after rebooting I am not getting it now..
Also all of a sudden a red boundary started to appear at the edges of the screen. So I though I had opted for the screen refresh notification in the Developer options but I had not. Still i could see the red rectangle when the screen refreshed. I had to reboot the system. Now fine.
Hi guys,
I recently updated my to cm14 ( nightly 25-11-2016) which got my op3 to 7.0.1 however all apps crashed right after boot and wifi wasn't working. So I tried to factory reset it and now my phone can't bootup anymore.
also recovery mode is inaccessable.
Any suggestions and helps are welcome
thank you!
JohnBillyHill said:
Hi guys,
I recently updated my to cm14 ( nightly 25-11-2016) which got my op3 to 7.0.1 however all apps crashed right after boot and wifi wasn't working. So I tried to factory reset it and now my phone can't bootup anymore.
also recovery mode is inaccessable.
Any suggestions and helps are welcome
thank you!
Click to expand...
Click to collapse
all apps crashed right after boot
Dirty Flashed?
You need to flash twrp recovery through your computer again.
boot into the recovery
after that clear cache/dalvik/art , data , system
flash your rom
done.
G0dofWar said:
all apps crashed right after boot
Dirty Flashed?
You need to flash twrp recovery through your computer again.
boot into the recovery
after that clear cache/dalvik/art , data , system
flash your rom
done.
Click to expand...
Click to collapse
thank you Kratos! just got it fixed!
go kill a god!
Backround: I'm was on Open Beta 10 with blu spark twrp. On a oneplus 3
I saw this new update and I knew I had twrp so I was going to download the update, boot into twrp then reboot to system to have oneplus recovery take over. Once I hit upgrade now, after downloading the update, It did its "preparing to upgrade" then booted to twrp. It asked me for a password I didn't have so I hit cancel went into TWRP hit reboot to system and now it is stuck in bootloop. Please help :crying:
I had the same problem...
i downloaded the latest image (4.0.1) and installed it through twrp and i have the same issue... anyone can help? this thing with the new android version tends to be super annoying
Any solution?
Kaise18 said:
Any solution?
Click to expand...
Click to collapse
I did the same thing for the newest update 4.0.2 and still the same problem. now im reading things here and in oneplus forums and it seems a lot of ppl have the same issue but i havent read a fix yet... its kind of frustrating.
kabrty said:
Backround: I'm was on Open Beta 10 with blu spark twrp. On a oneplus 3
I saw this new update and I knew I had twrp so I was going to download the update, boot into twrp then reboot to system to have oneplus recovery take over. Once I hit upgrade now, after downloading the update, It did its "preparing to upgrade" then booted to twrp. It asked me for a password I didn't have so I hit cancel went into TWRP hit reboot to system and now it is stuck in bootloop. Please help :crying:
Click to expand...
Click to collapse
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/
I'll give it a try, thanks
Just flashed stock recovery, and my phone updated and I'm back in, yay!