Related
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
kaemon said:
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
Click to expand...
Click to collapse
Try this TWRP form arter... this is the only TWRP being use by many of us here.. you flash it through odin or recovery...
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
fabiok81 said:
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
Click to expand...
Click to collapse
The issue is not the kernel... its the recovery that doesn't work when reboot to system is touch and is freezing..
Go to advance then terminal
Write reboot
Easy!
Yes i know the iusse is about the recovery but it seems because there is not compatibility between some recovery and some kernel. I tried various recovery 3.0 and i have always a kind of freeze. The TWRP... by Manhit for example gave me freeze with xspace kernel but not with hacker kernel. I don't no the reason....
Inviato dal mio SM-G925F utilizzando Tapatalk
same but different
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
wahwahward said:
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
Click to expand...
Click to collapse
Try with hacker kernel. Wipe cache but not data
callumbr1 said:
Try with hacker kernel. Wipe cache but not data
Click to expand...
Click to collapse
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
wahwahward said:
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
Click to expand...
Click to collapse
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
callumbr1 said:
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
Click to expand...
Click to collapse
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
wahwahward said:
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
Click to expand...
Click to collapse
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
callumbr1 said:
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
Click to expand...
Click to collapse
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
wahwahward said:
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
Click to expand...
Click to collapse
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
callumbr1 said:
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
Click to expand...
Click to collapse
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
wahwahward said:
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
Click to expand...
Click to collapse
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
callumbr1 said:
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
Click to expand...
Click to collapse
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
wahwahward said:
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
Click to expand...
Click to collapse
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
callumbr1 said:
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
Click to expand...
Click to collapse
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
wahwahward said:
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
Click to expand...
Click to collapse
I think it normally means a failed update. Sometimes there are instructions to use smart switch other times it just means the update failed.
Try with the custom ROM and keep me updated.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.
Hi!
Finally I got stuck in a boot loop on my Pixel 6 running QPR2.
It's looping after the G animation (vibrates a few times at that point when attached to a PC).
Reflashing the latest QPR factory image (without -w) by using SDK 33.0.3 does not solve the issue.
The ROM was running fine before, but it rebooted due to a faulty custom kernel version and now I'm stuck.
My theory is, that the launcher (nova) can't load and therefore it reboots.
Anything I could do using fastboot?
Never flash a custom kernel on a stock ROM, If not suggested by the dev.
I understand that you flash without wipe?
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If the kernel broke your actually ROM, nope. You could backup the file stored locally via adb in the recovery, but not anything more.
Wipe all is the best, better than have to handle with an hard brick.
Sui77 said:
Done that for years without any issue.
The last version of the custom kernel had an issue and caused reboots.
Not sure if this is the ulprit, but normally that should be solved by flashing factory image without -w.
So the question is: Is there any other option than doing a factory reset?
Click to expand...
Click to collapse
If I were you I'd maybe get some logs and go through them and see if you can find anything that way. Maybe add logs to your op here.
There aren't many ways to backup things nowadays for pixel 6 but what I have used to backup apps + app data that works well when restoring is Neo app from Fdroid store. As far as backing up goes, at this time I've used nothing that is/has been as solid as Neo. I miss the days of just being able to boot one of a few various custom recoveries, making a nandroid backup to a USB thumb drive with my OTG cable and restore it whenever it was needed but things change. Sounds like maybe something was left behind from your kernel install. If you really dislike formatting I'd stay away from whatever you installed here to get in this loop but definitely backup using Neo once you get going again and put your backups on thumb drive or you PC or somewhere other than your device so you can restore them when you need to. I don't flash nowhere near as much as I used to but I used to flash my device(s) many times a day , everyday for many years but I remember years ago on another device I looped and wiped my cache and system and reflashed rom and ended up booting up. But that was another device years ago. Maybe try adb sideloading instead of factory image flash without wiping data. Try that and after it's done installing reboot to others slot and sideload it again... These things probably won't work but you never know until you try. Did you have magisk installed before and not now? Maybe flash stock kernel patched with magisk to both slots if so. Hate to say it but you will probably end up having to format data but idk because I don't know exactly how you installed the kernel "in detail" or exactly what kernel it is or if anything else was changed from before you looped ... No logs...
I've been using Android since the beginning (G1) and I've been tinkering with my devices since back in the Nexus S days on a regular basis and I've found that the best way for to get the help I need is to try like hell to figure whatever it is out myself by searching for the problem I'm having, I mean like really searching, sometimes for hours , sometimes maybe searching for things related to the problem I'm having that show up in my searches, sometimes the answer can be in another devices forum, piecing together bits of info from various places to try and solve whatever it is... etc ... etc... But the best way to get help is do research on it, take some notes, try various things to fix it, then if I still can't figure it out make a post about it here and in op attach every log I can possibly gather from said device, include all the things I tried to fix it with myself "in detail..." My exact installation process, you know like: reboot bootloader, was on slot A, executed ./flash-all.sh for factory image xxxxx, rebooted system ... The more details you provide the more accurate people will be when answering and the more people you will get to reply.. I'm not trying to sound like some asshole or anything at all. Im just speaking what works best here to get answers. Sometimes you just don't get any answers even if you post 18 paragraphs with a chart and a line graph, things you tried, what all you tried it with and links to it all. But anyone here who does this will most definitely stand a much better chance at getting some replies on whatever it is. I sometimes read over on Reddit and Tele groups , sometimes answers can be found that way. Sometimes people just give you the silent treatment.. Even if you do your homework. That's just a thing with anything related to development that happens. I always used to think when I would get no replies that the other guys and gals who know the answer are thinking to themselves, "oh look at this idiot here!" "He clearly didn't graduate from Harvard top of his class with a PhD like we did. " " Such an imbecile!!! " But what could have been going on and more than likely was/is is life , kids, bills, sleep, relationships, covid19, and tons of other things..
Some of this development stuff is a real beech to get and everyone works hard to get it and many aren't too fond of just giving random people answers that took them many sleepless nights to get. But if and when a dev sees someone with a detailed post , things tried.... etc ... etc .. Theyre much more likely to throw some knowledge your way. That's been my experience anyway.
@flash713
Wow, thx for thw write up, appreciate!
I was on latest QPR2.1 with Radioctive Kernel, Magisk installed.
Since the device got stuck in the boot animation, I tried a lot and flashed different factory images using the flash-all method. w/o success.
Also tried the Flash tool in the google website, also w/o success.
When the device boots while it's connected to the PC, it beeps/vibrates 3 times and the reboots.
My guess is that it has problems to load the launcher, Nova was set as standart.
I'm using android since years, tinkering a lot, but I'm not a pro in doing so.
Meanwhile i set up my new Pixel 7 and restored it via Google backup and a few apps by using a SWIFT backup.
Fotos were restored by Google, but all whatsapp pictures are messed up ow, cause the date of restore.
How do I gather proper logs?
Did a last attempt and sideloaded the OTA to both slots...same outcome...
Doesn't magisk have a remove all modules.zip? I mean oriole doesn't have TWRP available yet.
I presume that when it's bootlooping you don't have any ADB?
You did have ADB enabled, right?
Depending on system and setup you may have ADB started by init or started by Android.
Your problem could be as simple as a bad Launcher.
I don't know if the P6 has a UART console. Does it?
Hi Renate,
thx for your reply.
Yes, that is what i thought. The Pixel boots up into the G-animation and then loops 3 times (beeping/vibrating if connected to PC) and than reboots in total.
I think I had something like that in the past when I accidently deleted the launcher apk (don't ask )
Anyway, Nova launcher was set as standart, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Sui77 said:
Anyway, Nova launcher was set as standard, so the only idea could be to set the genui Pixel launcher as default, but I don't know how to do that in fastboot or adb mode.
Click to expand...
Click to collapse
I'm still not clear if you have ADB ever available.
If you do you could:
Code:
adb uninstall com.nova.whatever.launcher
If the /data/data that Nova is using is corrupt or missing it could cause failure.
Android will switch to whatever else belongs to android.intent.category.HOME automatically.
If there is nothing there you can install another launcher.
Have adb (after booting into recovery mode), will report back asap
I habe adbd device connected via recovery/rescue mode, but that's not working.
In bootloader, I can't use adb, no device connected.
Hw can I use adb while the device is not booted up?
Can you mount data in recovery (and it's unecrypted)?
Feeling a bit dumb, but I can only boot into fastboot or into the boot loop, don't know how to mount data in recovery mode (the one with the andoird robot)
When you're in the boot loop you don't get adb even for a few seconds?
This are the last lines of the recovery.log
2 new items by TheMrSui
photos.app.goo.gl
Checked that by opening a cmd and using "adb devices", but nothing showed up
When you're viewing that log, don't you have ADB working then? It says that it is.
I had this weird issue on Raven, first try using android flash tool through a chrome based browser. If that still loops then wipe, and flash an older image. For some reason I had to flash an image from the previous month and that would boot.