Related
I've tried in twrp and cwm/cwm touch - I get a boot loop no matter which rom I flash
I made a backup of my stock 404 on cwm and twerp so It's easily reversible in either.
Similar to this post - http://forum.xda-developers.com/showthread.php?p=45795997#post45795997
It involves flashing Pi-llama 1.4 via adb and then installing the custom rom over the top.
Ran into all sorts of issues, would hang on the third data write, so I cancel it and then it would continue etc... and install
Now I'm up and running I've got half PiLlama and this rom I put on, battery drain is bad and the clock process crashes when I try and set an alarm. Otherwise it's great.
Any ideas? Seems to be the data partition causing the problems.
I'm rooted and unlocked, thought I'd add.
Flacid Monkey said:
I've tried in twrp and cwm/cwm touch - I get a boot loop no matter which rom I flash
I made a backup of my stock 404 on cwm and twerp so It's easily reversible in either.
Similar to this post - http://forum.xda-developers.com/showthread.php?p=45795997#post45795997
It involves flashing Pi-llama 1.4 via adb and then installing the custom rom over the top.
Ran into all sorts of issues, would hang on the third data write, so I cancel it and then it would continue etc... and install
Now I'm up and running I've got half PiLlama and this rom I put on, battery drain is bad and the clock process crashes when I try and set an alarm. Otherwise it's great.
Any ideas? Seems to be the data partition causing the problems.
Click to expand...
Click to collapse
Damn! Please can someone move this to http://forum.xda-developers.com/razr-i/help Posted it in here by accident
I you want to flash a custom rom just don't wipe data and don't do a format /wipe data
The problem with that is it has previous rom stuff still installed.
I like a clean fresh install of a rom, so no contacts, messages, apps etc...
There is no way to do this without a bootloop.
Flacid Monkey said:
The problem with that is it has previous rom stuff still installed.
I like a clean fresh install of a rom, so no contacts, messages, apps etc...
There is no way to do this without a bootloop.
Click to expand...
Click to collapse
flash a stock rom via rsd-lite..this will wipe the data too..then flash a custom rom
antkalaitzakis96 said:
flash a stock rom via rsd-lite..this will wipe the data too..then flash a custom rom
Click to expand...
Click to collapse
Boot loop.
Get to the rom boot animation and it does the updating apps then boot loops back to the moto screen and rom animation then repeats until i power off and restore a backup.
Thank you both for suggestions so far. Getting closer to solving
Sent from my XT890 using XDA Premium 4 mobile app
Flacid Monkey said:
Boot loop.
Get to the rom boot animation and it does the updating apps then boot loops back to the moto screen and rom animation then repeats until i power off and restore a backup.
Thank you both for suggestions so far. Getting closer to solving
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
u using cwm?
before flash a rom -> wipe data /system / cache! / dalvik chache -> then flash!
if this dont help do above + wipe battery stats then flash the rom.
have fun.
regards
pangyaaaaaa said:
u using cwm?
before flash a rom -> wipe data /system / cache! / dalvik chache -> then flash!
if this dont help do above + wipe battery stats then flash the rom.
have fun.
regards
Click to expand...
Click to collapse
Yes, I'm using cwm. Tried touch and twrp.
Tried the above, same bootloop.
Only works if i leave my stock 404, push pillama 1.4 via adb and then flash the custom ROM over that in cwm.
This leaves residue from 404 and pillama on my phone though.
Sent from my XT890 using XDA Premium 4 mobile app
Flacid Monkey said:
Yes, I'm using cwm. Tried touch and twrp.
Tried the above, same bootloop.
Only works if i leave my stock 404, push pillama 1.4 via adb and then flash the custom ROM over that in cwm.
This leaves residue from 404 and pillama on my phone though.
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does stock 404 mean, you are still on ICS?
If so why don't you flash JB with RSD-Lite and try again installing a custom rom?
Can u make a logcat about it?
ICuaI said:
Does stock 404 mean, you are still on ICS?
If so why don't you flash JB with RSD-Lite and try again installing a custom rom?
Click to expand...
Click to collapse
Trying this now
Hazou said:
Can u make a logcat about it?
Click to expand...
Click to collapse
Will try the above then if it doesn't work I'll log it :good:
So I tried RSD lite with Android 4.1.2 Blur_Version.91.2.26001.XT890.Retail.en.EU
No dice. Failed at 7/16 System_Signed
This royally put me in a bad place. 45 minutes of ADB later, I'm back on my CWM backup of 404.
Gonna clean the logs and start from scratch
Flacid Monkey said:
So I tried RSD lite with Android 4.1.2 Blur_Version.91.2.26001.XT890.Retail.en.EU
No dice. Failed at 7/16 System_Signed
This royally put me in a bad place. 45 minutes of ADB later, I'm back on my CWM backup of 404.
Gonna clean the logs and start from scratch
Click to expand...
Click to collapse
I have the same problem and I am on Stock 4.1.2. I have given up and no longer have a rooted phone with a custom ROM. I would, however, be grateful if someone could find a solution
If you are on 404 and trying to get to 4.1.2 you can root your phone then use the following method to unroot and install 4.1.2. You can then root again if you wish.
http://forum.xda-developers.com/showthread.php?t=2398347
grampsharry said:
I have the same problem and I am on Stock 4.1.2. I have given up and no longer have a rooted phone with a custom ROM. I would, however, be grateful if someone could find a solution
If you are on 404 and trying to get to 4.1.2 you can root your phone then use the following method to unroot and install 4.1.2. You can then root again if you wish.
http://forum.xda-developers.com/showthread.php?t=2398347
Click to expand...
Click to collapse
Thank you will give that a go.
I've got a problem now after trying the official 4.1.2 upgrade which failed miserably, the boot image has changed to the warning unlocked phone bla bla bla
My SMS centre number keeps disappearing stopping texts sending. Receiving and calling work fine. Tried the fixes online but all work for two minutes then it disappears again.
Can't factory reset, just boots back up with everything as it was when it turned off. Can't get into the stock recovery so stuck with CWM or twrp
Any time I flash a rom it boot loops.
Ideas on how I can get a clean official 4.1.2 onto the phone? Re-lock bootloader, remove root and then try?
So locking bootloader and removing root does not work.
I'd advise anyone that doesn't know what they're doing to avoid it.
It pretty much soft bricked my phone.
I've started a new thread in q&a with another issue regarding multi flash in fastboot hanging on the third or fourth download.
Im certain parts of the 4.1 are still there even after formatting everything in cwm and restoring my original backup.
Having network issues, 3g and wifi etc are fine. Sms, calls and anything to do with changing network operator just stops a few minutes after boot. I can still receive fine which is odd.
What's the deal with putting a radio on over an official ROM? Yey or ney
Sent from my XT890 using XDA Premium 4 mobile app
I have an HTC One on sprint, running a CM11 nightly. While I liked it for a while, due to business aspects, I need to go back to iphone. I am just gonna trade someone I know for my HTC for their iphone. I guess what i was wondering is what is the process of returning it back to stock? They still want root access, just not a custom ROM. I'm S-ON, HBOOT 1.56.000, Radio, 1.00.20.1100, and OS 4.06.651.4.
I'd like a step by step process hopefully (not an expert on androids, more used to iphones). But i do have some experience with cmd. I was also wondering if I turn it back to stock, will i lose all of my data (contacts, photos,etc.) I know you lose apps, but when I flashed to CM11, I backed up with TWRP, and then had to use CWM, so i couldn't restore my contacts. I do have a backup of my original ROM before i went to CM11 in TWRP, but I had to flash to CWM, so I'm not sure if it's still there.
Also, if they wanted to keep the CM11 on it, would there be any problems switching phone numbers and whatnot on it? I'd assume not because it still has an IMEI, but just wanted to make sure.
Find a flashable zip of twrp and if you didn't delete it ur backup of ur stock rooted should work...u have to have Sprint base Rom to swap phones so NO cm11 will not work when you go to trade phones
Sent from my HTCONE using Xparent Red Tapatalk 2
noXcape said:
Find a flashable zip of twrp and if you didn't delete it ur backup of ur stock rooted should work...u have to have Sprint base Rom to swap phones so NO cm11 will not work when you go to trade phones
Sent from my HTCONE using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I tried to reflash twrp. It wouldnt work. it wouldnt recognize touches.
So if I want it all stock, except for root, can I use an RUU? I know it wipes everything, but better than nothing. plus i could sync with htc manager and get everything i had back.
FireGuy2014 said:
I tried to reflash twrp. It wouldnt work. it wouldnt recognize touches.
So if I want it all stock, except for root, can I use an RUU? I know it wipes everything, but better than nothing. plus i could sync with htc manager and get everything i had back.
Click to expand...
Click to collapse
what version of twrp did you flash, should be 2.6.3.0 or higher. thus the touch problems, you don't need to ruu.(openrecovery-twrp-2.6.3.0-m7wls.img)
Aldo101t said:
what version of twrp did you flash, should be 2.6.3.0 or higher. thus the touch problems, you don't need to ruu.(openrecovery-twrp-2.6.3.0-m7wls.img)
Click to expand...
Click to collapse
I used that originally i believe. So if I re-flash my recovery to twrp, I can restore from my back up, even if I was rooted? and would i still have CM11, or stock sense?
FireGuy2014 said:
I used that originally i believe. So if I re-flash my recovery to twrp, I can restore from my back up, even if I was rooted? and would i still have CM11, or stock sense?
Click to expand...
Click to collapse
yep, you'll still have the same rom after flashing recovery til you restore a previous backup, you can back up cm 11 too.
Aldo101t said:
yep, you'll still have the same rom after flashing recovery til you restore a previous backup, you can back up cm 11 too.
Click to expand...
Click to collapse
I'm selling it and the person wants a stock rom, but also rooted. So Would I have sense or CM11 if i flash my twrp and restore my backup?
FireGuy2014 said:
I'm selling it and the person wants a stock rom, but also rooted. So Would I have sense or CM11 if i flash my twrp and restore my backup?
Click to expand...
Click to collapse
if your backup is stock sense it will be sense.i have no idea what your backup is. you should know that.
Aldo101t said:
if your backup is stock sense it will be sense.i have no idea what your backup is. you should know that.
Click to expand...
Click to collapse
I tried using the twrp manager from the play store but it says I'm not supported. 2.7.0.0 is the latest. It shows the backup i have though. Does anyone know where I can download it from and flash it onto my phone?
FireGuy2014 said:
I tried using the twrp manager from the play store but it says I'm not supported. 2.7.0.0 is the latest. It shows the backup i have though. Does anyone know where I can download it from and flash it onto my phone?
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/m7wls is where to go 2.7.0.1 is the latest, flash this with adb fastboot, in your bootloader
Aldo101t said:
http://techerrata.com/browse/twrp2/m7wls is where to go 2.7.0.1 is the latest, flash this with adb fastboot, in your bootloader
Click to expand...
Click to collapse
would the command be fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img?
FireGuy2014 said:
would the command be fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img?
Click to expand...
Click to collapse
yessir
Aldo101t said:
yessir
Click to expand...
Click to collapse
should i erase my cache first?
Or just plug it up, go to bootloader, and flash it, then restore?
FireGuy2014 said:
should i erase my cache first?
Or just plug it up, go to bootloader, and flash it, then restore?
Click to expand...
Click to collapse
not sure on the cache erase some say do some say don't i'd try it without first if you have issues wipe it and reflash recovery
Aldo101t said:
not sure on the cache erase some say do some say don't i'd try it without first if you have issues wipe it and reflash recovery
Click to expand...
Click to collapse
tried to no avail. I tried and it was stuck on HTC logo for 15 minutes. I reflashed to CM11, and im downloading the RUU now to completely wipe/restore it. Unless i did something wrong? I erased cache using adb, then booted up, restored my stuff, and it said successful, but it was on the htc logo. I tried again to the same thing. then i reflashed cm11 and it worked. did i forget to do a factory reset before i restored everything? it said it wiped stuff before it restored it.
FireGuy2014 said:
tried to no avail. I tried and it was stuck on HTC logo for 15 minutes. I reflashed to CM11, and im downloading the RUU now to completely wipe/restore it. Unless i did something wrong? I erased cache using adb, then booted up, restored my stuff, and it said successful, but it was on the htc logo. I tried again to the same thing. then i reflashed cm11 and it worked. did i forget to do a factory reset before i restored everything? it said it wiped stuff before it restored it.
Click to expand...
Click to collapse
after you erased cache did you flash recovery, then reboot recovery and restore a backup
when you are on the htc logo hold the power button down til it reboots and see if it goes past the htc screen
you don't have to factory reset to restore a rom just hit restore and select the backup
Aldo101t said:
after you erased cache did you flash recovery, then reboot recovery and restore a backup
when you are on the htc logo hold the power button down til it reboots and see if it goes past the htc screen
Click to expand...
Click to collapse
I flashed recovery, then erased cache, then rebooted to recovery, and restored a backup. when it said successful, i rebooted from there, and it vibrated on bootup, but stayed at the htc screen for a while. I held the power button and rebooted. same thing.
FireGuy2014 said:
I flashed recovery, then erased cache, then rebooted to recovery, and restored a backup. when it said successful, i rebooted from there, and it vibrated on bootup, but stayed at the htc screen for a while. I held the power button and rebooted. same thing.
Click to expand...
Click to collapse
well, i don't know, i'd try 2.6.3.0 twrp and don't wipe cache, thats what i been using, what the hell can't hurt to try at this point in the game
sometimes it takes awhile on the first boot, i've had some take quit awhile, but i don't know
Aldo101t said:
well, i don't know, i'd try 2.6.3.0 twrp and don't wipe cache, thats what i been using, what the hell can't hurt to try at this point in the game
Click to expand...
Click to collapse
I'm gonna try an RUU. I'm downloading the latest one right now (4.06.651.4 i believe). I'll let you know how it works out. since i'm S-ON, all i need to do is relock boot loader and then run the RUU correct?
FireGuy2014 said:
I'm gonna try an RUU. I'm downloading the latest one right now (4.06.651.4 i believe). I'll let you know how it works out. since i'm S-ON, all i need to do is relock boot loader and then run the RUU correct?
Click to expand...
Click to collapse
yes,
Here is the problem. I accidentally deleted everything on my Nexus, so now I have no operating system. I am trying to flash stock android 6.0 and I recieve the error "package missing system.img". My phone was already running Marshmallow, and I had no problems installing it the first time, so I am not quite sure why this is happening now.
Majava42 said:
Here is the problem. I accidentally deleted everything on my Nexus, so now I have no operating system. I am trying to flash stock android 6.0 and I recieve the error "package missing system.img". My phone was already running Marshmallow, and I had no problems installing it the first time, so I am not quite sure why this is happening now.
Click to expand...
Click to collapse
easy one to solve as its written around so many times.. do not use the flash-all script, you have to flash each partition individually.
simms22 said:
easy one to solve as its written around so many times.. do not use the flash-all script, you have to flash each partition individually.
Click to expand...
Click to collapse
I did this but it got stuck in a boot animation.
Majava42 said:
I did this but it got stuck in a boot animation.
Click to expand...
Click to collapse
try it again. if you get stuck in a bootloop, go back and wipe data/factory reset.
simms22 said:
try it again. if you get stuck in a bootloop, go back and wipe data/factory reset.
Click to expand...
Click to collapse
I tried this 3 more times and it still got stuck in a bootloop, should I keep trying?
Are you using a toolkit to flash?
Sent from my Nexus 6
Majava42 said:
I tried this 3 more times and it still got stuck in a bootloop, should I keep trying?
Click to expand...
Click to collapse
Try reflashing boot.img.
Worked for me.
Did you ever find a solution to this problem? I'm curious now! I've heard of people having this problem before, I started flashing them individually for this reason! You can NEVER be too safe when doing something like this. You get the hang of doing it individually after doing it so many times though.
Sent from my Nexus 6
Flashed SlimLP and had been succesfully using it for about a month before I decided to **** around with layers (Evolve and Commute specifically). When I reboot to apply it got stuck on the boot animation, I left it to charge overnight and it was still stuck in the morning. Tried wiping the cache partition but don't want to do a factory reset if there's a way to salvage it (nothing too vital, just pain in the ass having to reinstall all my apps, etc.)
Total noob to flashing and ROMS, etc. No backups that I know of, not sure if there's a custom recovery. Only found the Amazon one and Fastboot mode.
terkrockerfeller said:
Flashed SlimLP and had been succesfully using it for about a month before I decided to **** around with layers (Evolve and Commute specifically). When I reboot to apply it got stuck on the boot animation, I left it to charge overnight and it was still stuck in the morning. Tried wiping the cache partition but don't want to do a factory reset if there's a way to salvage it (nothing too vital, just pain in the ass having to reinstall all my apps, etc.)
Total noob to flashing and ROMS, etc. No backups that I know of, not sure if there's a custom recovery. Only found the Amazon one and Fastboot mode.
Click to expand...
Click to collapse
How did you flash slimlp?
Sent from my KFFOWI using XDA Labs
sd_shadow said:
How did you flash slimlp?
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Flashfire
terkrockerfeller said:
Flashfire
Click to expand...
Click to collapse
do you know which stock system version it was on?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
do you know which stock system version it was on?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
5.1.
terkrockerfeller said:
5.1.
Click to expand...
Click to collapse
you tried wiping cache in Stock recovery?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
you tried wiping cache in Stock recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Yup
You are lucky you can still access the stock recovery. If your device had 5.1.1 then reinstall FireOS 5.1.1 via stock recovery. From that point you can re-root & reinstall your rom + apps & stuff.
Be thankful you're not bricked & don't screw with layers if you don't have a 5.0.1 device. The Fire does not play well with many layers.
blueberry.sky said:
You are lucky you can still access the stock recovery. If your device had 5.1.1 then reinstall FireOS 5.1.1 via stock recovery. From that point you can re-root & reinstall your rom + apps & stuff.
Be thankful you're not bricked & don't screw with layers if you don't have a 5.0.1 device. The Fire does not play well with many layers.
Click to expand...
Click to collapse
Don't know what happened but I can't seem to access the stock recovery any longer. Fastboot mode still works, though. What do I do from here?
Edit: scratch that, I got to the recovery menu again
terkrockerfeller said:
Flashed SlimLP and had been succesfully using it for about a month before I decided to **** around with layers (Evolve and Commute specifically). When I reboot to apply it got stuck on the boot animation, I left it to charge overnight and it was still stuck in the morning. Tried wiping the cache partition but don't want to do a factory reset if there's a way to salvage it (nothing too vital, just pain in the ass having to reinstall all my apps, etc.)
Total noob to flashing and ROMS, etc. No backups that I know of, not sure if there's a custom recovery. Only found the Amazon one and Fastboot mode.
Click to expand...
Click to collapse
I know on my nexus 6P it has a overlay folder, if you delete that it should delete your layers that you added(if that folder exists on this)
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
panamera2011 said:
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
Click to expand...
Click to collapse
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
bfürbanane said:
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
Click to expand...
Click to collapse
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
panamera2011 said:
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
Where does it say to install SuperSU? How would that be possible when Android is not booting.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
I'm sorry but it's really strange, never had installation issues with any version of this rom
Have you tried this kernel to install the rom?
https://www.androidfilehost.com/?fid=24052804347829437
Sent from my H60-L02 using Tapatalk
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Sorry but I confused the message with the MIUI 6.2.12 thread [emoji16]
Sent from my H60-L02 using Tapatalk
AutumQueen92 said:
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
Click to expand...
Click to collapse
I tried that. I went to samsung-updates.com and downloaded a version that I believe is compatible with my baseband version. Is there any way to check what baseband version my phone has? Then I flashed with odin and was stuck in a bootloop. I then flashed PhilZ recovery and the boot hangs at the samsung logo.
bfürbanane said:
Is there any way to check what baseband version my phone has?
Click to expand...
Click to collapse
Settings>about phone>
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
The phone is not booting.
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
Doh! sorry not reading what's in front of me. I did once read that you can get phone number via ADB, maybe the same will work for baseband?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
N00b... said:
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
Click to expand...
Click to collapse
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
bfürbanane said:
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
Click to expand...
Click to collapse
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Condox18 said:
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Click to expand...
Click to collapse
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
same problem
bfürbanane said:
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
Click to expand...
Click to collapse
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Condox18 said:
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Click to expand...
Click to collapse
Thanks for the pointer. I subscribed myself to that thread.