Develop Bugs

boot loop after flashing latest manhatten project rom

Ok have been running foxhound 1.1,tried a couple of other roms,kernels,etc and no problem. But now all of a sudden tried to flash manhatten and endless boot loop. I have tried to wipe from cwm several times but no luck. I dont want to lose my pictures from virtual sdcard. I have no access to adb but cwm and fastboot of course. I'm using linux so is there any way to use fastboot to erase everything but keep virtual sdcard. If that can you point me to instructions on how to from fastboot. I have the GSM version

Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot

Samsuck said:
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Click to expand...
Click to collapse
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????

tman7510 said:
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
Click to expand...
Click to collapse
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.

9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk

Samsuck said:
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
Click to expand...
Click to collapse
I have formatted everything but davik cache but when I do that I get" E:unknown volume for path /sd-ext Dalvik Cache Wiped " then reflash foxhound and now I am back to the boot loop all I get is Google with unlock symbol at the bottom and it just loops. There has to be a way to get info off my virtual sdcard..I dont care how hard it is

demon2112 said:
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I didn't use the gapps but the rom should still boot without that gapp version. Also shouldn't I be able to flash another rom without having this issue??? All I did was flash from clockworkmod. maybe the zip file I downloaded got corrupted but I am unable to fix the problem. I had installed the manhatten rom yesterday but went back to foxhound because lack of performance/undervolting settings that apperently are on the rom. just want it to work again..I'm unable to use adb becasue it wont boot. all I have is fastboot and cwm recovery

That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA

Samsuck said:
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Click to expand...
Click to collapse
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???

"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"

tman7510 said:
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
Click to expand...
Click to collapse
You can use ADB in CWM Recovery. I do it all the time in Windows.

El Daddy said:
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
Click to expand...
Click to collapse
yes I know and I have no problem using what little I know of fastboot commands but is there a way to use fastboot to copy my virtual sdcard to my pc?????

Be sure to "mount data" in Recovery
adb shell
type su for superuser.
then ls to list the dirs
and cd to change
You might have to pull files one by one. I'm not sure if there's a way to pull the entire contents of it.

Samsuck said:
You can use ADB in CWM Recovery. I do it all the time in Windows.
Click to expand...
Click to collapse
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!

Actually, do this.
Once you have the drivers installed for Windows, and your phone is being recognized "adb devices"
Run
adb pull /data/media/DCIM C:Urname\example\blah
Replace the C:Urname\example\blah with an actual directory of the Windows PC
It might take some time but that should drag your pictures and stuff.

Here's the link with instructions to return to stock. http://forum.xda-developers.com/showthread.php?t=1366806

tman7510 said:
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Click to expand...
Click to collapse
Hit, Install SDK on the toolkit. It will do it very quick and easy for you.
Since the SD Card on our Nexus is actually /data/media, like I said earlier, just mount data.

Gnex toolkit is a great tool. I'm wondering why I have permission issues with adb in cwm recovery in Linux. not complaining but I wish there was a kit like that for us linux users

any body know why in cwm recovery if run ./adb device in linux you get
devices listed
?????????? no permissions
any linux users out there? I'm saving my files thanks to a windows program gnex tookkit by mskip.
Special thanks to Samsuck for all his help and the rest of the forum

[Q] CWM Bootloop w/ v5.8.2.0

Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.

Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?

Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.

ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro

edit: re-ran superoneclick for run and it worked! I should be good from here

Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.

So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...

I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA

lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?

Tokie the dropbox links are not working

reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys

cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.

when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one

dd: can't open sdcard\boot.img : no such file or directory

i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it

Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.

drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image

I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.

If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol

Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol

[Q] Can I backup any data within fastboot?

Hi Folks,
I have experienced the sadly famous boot loop issue (the one that keeps the device on the boot screen forever), not in one, but in two different devices (same model and build, 4.0.2 GSM - ICL53F).
I fixed the first one by flashing the latest stock rom (4.0.4), but of course it lost all the data, including camera pictures.
So for this one, I would like to save as much as I can. The problem is, that I can't access the device with adb since it wont boot, I just can access it with fastboot.
I have managed to enter the ClockWorkMod Recovery and perform a backup, but it saves it into the sdcard, so if I flash the phone to fix it, it will lose the backup
So, the question is: How can I either access the filesystem trough fastboot or just performing a backup that won't be lost if I have to flash it.
Thanks in advance

You said you can access ADB...but I assume you meant can't?
If you can...
http://forum.xda-developers.com/showpost.php?p=24910351&postcount=21
And pull your sd card as well.
If not...
I assume you've tried booting into bootloader and odin?

Jubakuba said:
You said you can access ADB...but I assume you meant can't?
If you can...
http://forum.xda-developers.com/showpost.php?p=24910351&postcount=21
And pull your sd card as well.
If not...
I assume you've tried booting into bootloader and odin?
Click to expand...
Click to collapse
Your assumption is right, I can't.
And yes, I tried booting trough odin and bootloader, many times, but I have read about many people experiencing this issue, most of them solved it by wiping data (and some also flashing). I know how to solve the booting issue, I just want to save as much data as I can.

mdelolmo said:
Your assumption is right, I can't.
And yes, I tried booting trough odin and bootloader, many times, but I have read about many people experiencing this issue, most of them solved it by wiping data (and some also flashing). I know how to solve the booting issue, I just want to save as much data as I can.
Click to expand...
Click to collapse
No I understand man.
The link I gave would back up your apps at least...
And your SD if you changed -noshared to -shared but I haven't had much success.
But you'd need ADB access.
Wait for another opinion if you wish.
But I'd assume you need a factory reset if you can't get ADB...
And simply flashing a rom doesn't work, right?

mdelolmo said:
Hi Folks,
I have experienced the sadly famous boot loop issue (the one that keeps the device on the boot screen forever), not in one, but in two different devices (same model and build, 4.0.2 GSM - ICL53F).
I fixed the first one by flashing the latest stock rom (4.0.4), but of course it lost all the data, including camera pictures.
So for this one, I would like to save as much as I can. The problem is, that I can't access the device with adb since it wont boot, I just can access it with fastboot.
I have managed to enter the ClockWorkMod Recovery and perform a backup, but it saves it into the sdcard, so if I flash the phone to fix it, it will lose the backup
So, the question is: How can I either access the filesystem trough fastboot or just performing a backup that won't be lost if I have to flash it.
Thanks in advance
Click to expand...
Click to collapse
You cannot backup through fastboot with a shipping bootloader, but you can access /sdcard via adb when booted in CWM, despite not being able to connect when booted normally.
1) Boot into CWM.
2) Connect to a PC.
3) Open a command prompt in the same directory where you have your adb.exe file.
4) Type: adb pull /sdcard/

[Q] forgot to flash boot.img of Custom ROM - chaos!

Hi Guys,
I have a big problem! I forgot to flash the boot.img of "Jelly Bam 7.2.1" - it all ended in total chaos. I will try to describe everything I did, feel free to ask any further on points that seem to be more relevant than I thought.
To let you know: I have knowledge of flashing / custom roms and all that good jazz in general (with other phones before), but I am a total noob concerning all the One X specific stuff...
1.) rooted my One X. No problems so far, stock rom working fine after doing so, HBoot says "UNLOCKED" at the top, so no problems here.
2.) downloaded the custom ROM (JellyBam, endeavoru, 7.2.1), checked MD5, so no problems with the download - copied it to my phone
3.) went into recovery without fastboot, just the way via hboot and did the following in that order: "wipe data/factory reset", "wipe cache partition", formatted "/cache", formatted "/system", formatted "/data", "wipe dalvik cache", flashed the zip "jelly-bam-blabla.zip"
4.) tried to boot, which obviously did not work, because I forgot flashing the boot.img.... but in concrete: the phone first showed the normal "HTC"-Screen, then the JellyBam loading screen came on the screen, then the "Android Welcome Screen" showed up. after 0,5 seconds a pop-up came up saying "Unfortunately, System UI has stopped." and some 0,5 seconds after another pop-up places itself right over the other one. it says "Unfortunately, the process com.android.phone has stopped."... I tried to hit "OK" but it always came up again within 0,5 seconds or shorter.
5.) I went into hboot from there, because my first idea was, that the problem could have been me having forgotten the "fix permissions" after flashing the rom... so i did all the cache / formatting stuff again, flashed the zip again and then fixed permissions.
6.) tried to boot, exactly the same situation as described in "4"
7.) the boot.img-stuff came in my mind. slapped myself in the face several times. the "you should always fastboot flash your recovery if you want to flash anything on your phone"-advise also came in my mind. hurt my face for some more seconds.
8.) went into hboot again, then "fastboot", connected to my MBP and firstly tried to fastboot flash cwm-recovery. but the terminal said that my HOX is too low on battery life...
9.) the part I actually can't remember correctly. tried different advises on how to load the battery without having a rom up and running (from xda devs mainly) - which all did not work but somehow resulted in my HOX not even letting me boot up normally anymore. a (re)boot just kicks me directly into cwm recovery.
10) my battery went totally empty. and now the scary part i really do not understand begins: I connected my HOX via the usb cable to a power adapter. the orange light first started blinking, then it stood on for about 3 hours - I did not touch it. after these about 3 hours the device automatically booted into cwm recovery. i went into hboot which resulted in the normal error messages while connected via usb to a power adapter or a computer, so i unplugged the cable and rebooted recovery. again went in hboot, which now tells me I am too low on battery to flash anything. Because the orange light is only on in cwm recovery I thought that the phone charges there (I also read that, but the people said it would be veeery slow), so I tried to keep it in recovery. the problem is: it automatically shuts down after 20-30 minutes... I tried to avoid that as long as possible, always just hitting volume down once every 20 minutes - but even after doing that for about 6 hours, hboot still told me my battery is too low...
I really do not know what to do. I am never able to stay at home for longer than these 6 hours, so I do not know how I might get the battery high enough in order to flash the boot img or the zip in cwm again...
Please help me you genius people out there!
P.S.: The nerd video at registration is nicely done. I really like it. And I hope I did not overlook a thread that could solve my problem...

I'm not sure this is correct but I'd let it charge then in fastboot erase cache flash the boot then erase fastboot cache again.
A
Htc One X Viper 3.4.2

frontinsomething said:
Please help me you genius people out there!
Click to expand...
Click to collapse
At your service!!
Use this lil script to charge your device. It reboots the handset over and over again causing it to build up voltage. Once it prints out ~3750mV or higher, you should be good to flash.
http://forum.xda-developers.com/showthread.php?t=1658084

http://forum.xda-developers.com/showthread.php?t=1658084
Make this little script and execute it as a batch
Flash this recovery - http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Download the stock rom from here - http://forum.xda-developers.com/showthread.php?t=1546970
Fastboot flash the boot.img and `fastboot erase cache`
Wipe data and flash the rom.
You`ll at at least be in a working rom.
P.s you dont have to flash recovery all the time. Flash it once and leave it.

Iceax123 said:
I'm not sure this is correct but I'd let it charge then in fastboot erase cache flash the boot then erase fastboot cache again.
Click to expand...
Click to collapse
Yeah, my plan looked similar. The problem is you forgot the first stept. What I need is to
1.) somehow charge my phone to an adequate degree
2.) fastboot erase cache / flash boot.img / erase cache
3.) flash the zip again (just to make sure)
Can you help me for step one of that?
As described before the charging does not really work. In cwm it charges freakin slow, in hboot it does not seem to at all (I am not quite sure 'bout that)...

come on guys, you are way too fast in answering I knew why I like this place
I guessed people would come up with the script. the point is, that I tried that and failed at it... can somebody exactly tell me how to to that on Mac? I failed at it... (see step 9)

frontinsomething said:
come on guys, you are way too fast in answering I knew why I like this place
I guessed people would come up with the script. the point is, that I tried that and failed at it... can somebody exactly tell me how to to that on Mac? I failed at it... (see step 9)
Click to expand...
Click to collapse
I don't own a mac but it's really similar to Linux, so.....
Name it .sh instead of bat. And mark it executable by going to terminal as root and typing
Code:
chmod a+x [path_for_the_file]
Or use some gui to set it executable.
Then it should work by simply double clicking.
Good luck:good:
EDIT If fastboot commands different on mac, for example "fastboot-mac flash blablah", you need to modify the script accordingly.

TToivanen said:
I don't own a mac but it's really similar to Linux, so.....
Name it .sh instead of bat. And mark it executable by going to terminal as root and typing
Code:
chmod a+x [path_for_the_file]
Or use some gui to set it executable.
Then it should work by simply double clicking.
Good luck:good:
EDIT If fastboot commands different on mac, for example "fastboot-mac flash blablah", you need to modify the script accordingly.
Click to expand...
Click to collapse
Nice! At least the script works! Although it runs since 20:30 now and still only brought me up about 1mV... but let's see where I get. I will try to do all the good jazz if I get over 3680 - I will tell you as soon as it worked or if it did not.
See you later and thanks for the help so far!

frontinsomething said:
Nice! At least the script works! Although it runs since 20:30 now and still only brought me up about 1mV... but let's see where I get. I will try to do all the good jazz if I get over 3680 - I will tell you as soon as it worked or if it did not.
See you later and thanks for the help so far!
Click to expand...
Click to collapse
Nice ! Fingers crossed
Sent from my IceCold One X

TToivanen said:
Nice ! Fingers crossed
Sent from my IceCold One X
Click to expand...
Click to collapse
Just noticed, that I also need/want to flash the zip again - how much mV would I need for that?

Once you have flashed the boot image (fastboot batt warning vanished), you'll be good to flash the zip also.
Sent from my IceCold One X

You Are Epic, Guys!
Thank you for your help, not only, but mainly TToivanen!
Everything worked out fine! ROM is now up and running! yippieh!

Nice !
Enjoy the new ROM
Sent from my IceCold One X

No ROM installed, stuck in recovery.

I was getting random reboots and I tried to delete everything. I thought "clean to install new ROM" would just do a thorough cleaning.
When I try to boot it stays on the white HTC screen.
I can boot into the recovery and Squabbi's HTC One M8 toolkit reads it.
However, I have no idea what files to flash or even HOW to flash them so I can get an OS back on my phone. Can somebody please help?
I have no ADB experience.

Copy a rom zip on external sd and flash it through recovery or use a nandroid backup if you have one, but as you want a clean install maybe you want to use the first method

lukes91 said:
Copy a rom zip on external sd and flash it through recovery or use a nandroid backup if you have one, but as you want a clean install maybe you want to use the first method
Click to expand...
Click to collapse
Thank you for your reply. I am currently in ADB i tried to do "adb sideload" but got an error "failed to write data 'protocol fault (no status)'
I am going to try "adb push" right now and see if that works.
In the meantime, is it possible for me to recover using RUU in my current state of being stuck in recovery mode? Thanks again. I'll make sure to hit that donation button.

decko5 said:
Thank you for your reply. I am currently in ADB i tried to do "adb sideload" but got an error "failed to write data 'protocol fault (no status)'
I am going to try "adb push" right now and see if that works.
In the meantime, is it possible for me to recover using RUU in my current state of being stuck in recovery mode? Thanks again. I'll make sure to hit that donation button.
Click to expand...
Click to collapse
Well, the error might be a recovery issue, a cable issue (use stock htc one) or a driver issue... Unfortunately no RUU is available, so search for a nandroid backup in mr hofs' thread, copy it on the external sd card and recover it... Use the same recovery the backup was taken with (should be noted near the backup)... Let me know if you need further help dude

lukes91 said:
Well, the error might be a recovery issue, a cable issue (use stock htc one) or a driver issue... Unfortunately no RUU is available, so search for a nandroid backup in mr hofs' thread, copy it on the external sd card and recover it... Use the same recovery the backup was taken with (should be noted near the backup)... Let me know if you need further help dude
Click to expand...
Click to collapse
Ok so i found my nandroid backup and i am currently i am in adb. how do i push the backup to the TWRP backup directory?

decko5 said:
Ok so i found my nandroid backup and i am currently i am in adb. how do i push the backup to the TWRP backup directory?
Click to expand...
Click to collapse
It's easier to mount the storage in twrp, so you can browse it with the computer and copy paste the file inside... Then unplug the phone and restore the nandroid...
Edit: in this thread
http://forum.xda-developers.com/showthread.php?t=2318497
there are very useful infos for you, and there is the adb push command you are looking for (path should be the same)... Let me know if you recover everything or if you need more help

lukes91 said:
It's easier to mount the storage in twrp, so you can browse it with the computer and copy paste the file inside... Then unplug the phone and restore the nandroid...
Edit: in this thread
http://forum.xda-developers.com/showthread.php?t=2318497
there are very useful infos for you, and there is the adb push command you are looking for (path should be the same)... Let me know if you recover everything or if you need more help
Click to expand...
Click to collapse
I flashed TWRP via fastboot. then i pushed a nandroid backup hosted on this site to the /sdcard/TWRP/backsups/<a directory i made here> finally got everything working. Thanks again for everything. I just hope the random rebooting doesn't come back.
I think it was rebooting because I disabled some bloatware apps via an app called App Master, which requires root. And when i restarted the phone, all those apps tried to run again but there was a conflict with App Master.

decko5 said:
I flashed TWRP via fastboot. then i pushed a nandroid backup hosted on this site to the /sdcard/TWRP/backsups/<a directory i made here> finally got everything working. Thanks again for everything. I just hope the random rebooting doesn't come back.
I think it was rebooting because I disabled some bloatware apps via an app called App Master, which requires root. And when i restarted the phone, all those apps tried to run again but there was a conflict with App Master.
Click to expand...
Click to collapse
Well, you can try to reinstall the rom without removing the bloatware... If it's stable you found the culprit