Database Info

[Q] CWM not working right on new MT

I'm having all kinds of trouble with my MT. I originally flashed CM7 from stock with CWM after wiping factory and cache. The flash errored out the first time, but worked the second time. The gapps install errored out so I just tried rebooting without stock google apps. The phone just booted to the Motorola logo and didn't go any farther. I let it sit for over 20 minutes and no go.
I had made a backup so I went back to CWM to restore the phone. Again, I did a factory and cache wipe, ran the restore, rebooted, but now the phone boots to Motorola logo, then reboots into CWM. So weird!
I have a theory that it has something to do with a hardware problem. When I try to flash another rom (besides cm7) the screen goes blank (no text) and then goes back to the root menu. I tried booting to CWM then plugging it in and removing the battery but after an varied amount of time the phone shuts off.
I've searched and searched and I can't find where anyone's had a problem like this and NOT been able to get the phone back. I'd like a solution, but I'd also like to know if i'm the only one who's had this problem!
thanks!

Never mind
I got it working! I tried a different battery in it and it worked! I'm not sure if it was the battery or I just did the right combination of things, but I'm glad to be back! But for anyone who is having the same issue here's what I did:
Running CWM 5.0.2.6
1. Wipe factory/cache/davlik
2. format sd card
3. shut down
4. use pc to copy stock nandroid backup from androidforums (google "stock triumph restore")
5. boot back to CWM,
6. restore the backup and reboot, should work
**IF you have md5 checksum error, use adb via usb to run these commands and immediately try to restore again:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
# exit
**Make sure to unmount the sd card before restore.
Again, I really don't know if it was battery or not, but I tried this before changing batteries and it didnt work!

But wait, there's more!
Ok, now that I'm able to get back to stock, I'm still unable to flash any custom roms. I wipe/factory reset, format /system, then install update from sd card. When I confirm the update, the screen goes blank (no text), then goes back to the main menu! It does this with any rom!
Any help?

dont think triumph is supported phone according to cwm ?

garrmack said:
Ok, now that I'm able to get back to stock, I'm still unable to flash any custom roms. I wipe/factory reset, format /system, then install update from sd card. When I confirm the update, the screen goes blank (no text), then goes back to the main menu! It does this with any rom!
Any help?
Click to expand...
Click to collapse
You want to choose zip from sd card. Not install update
Sent from my VS910 4G using xda premium

I knew I'd word something wrong
I meant to say that. I did install zip from sd.

garrmack said:
I meant to say that. I did install zip from sd.
Click to expand...
Click to collapse
Are you running the latest cwm?
Sent from my VS910 4G using xda premium

Yep, 5.0.2.6. I just tried CM7 .04 beta because I have a friend who flashed it successfully on his MT. When I ran it it said it was installing for maybe 4 seconds and then said complete. When I rebooted all I got was the Motorola logo.
I just got this phone. Is it possible that Motorola changed something with the hardware to make it not work?

I've managed to get CWM running a little more stable by replacing the boot.img file with the one from CM7, but all I get when I run the zip is this:
-- Installing /sdcard/CM7.zip
Finding update package...
Opening update package...
Installing update...
Install from sdcard complete.
that all takes about 6 seconds and I get just the motorola logo when I reboot.
It still goes blank (no text) when I try to flash any other rom (like stockROM) so something is definitely screwy.

I don't know if this has anything to do with it, but I have a friend with a Triumph who successfully flashed cm7. I looked at his phone and found that the model number on his is WX345 while mine is WX435. Maybe my version really does have issues with clockwork?

vizionforever said:
dont think triumph is supported phone according to cwm ?
Click to expand...
Click to collapse
I did notice that the Triumph isn't listed on Clockwork's site. It is, however, listed on xda. Maybe its not officially supported?

figured it out! It had something to do with the sd card. I was using a 16gb class 10 PNY card. I put the stock 2gb back in it and it worked like a charm. Don't know if it was a defective card or the phone/clockwork just didn't like it.

Bay PONY...Noticed that my pny class 10 16gb was slower(or just took longer to mount and search for media, cause it's bigger) than the 16gb samsung class 2 that came with my epic...Dunno; but glad to hear CWM works! now you can switch back cards
PS. what root method u use command line or gingerbreak?

vizionforever said:
PS. what root method u use command line or gingerbreak?
Click to expand...
Click to collapse
I've tried both. I like the gingerbreak b/c it adds superuser app for you. Both worked fine though...
But since I installed CM7 I didn't need to root it first.

[HELP?] Soft-Brick?

So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing

powercamg4 said:
So i decied to go to carbon rom because my phone has been acting strange, YouTube would keep resigning in everything i would launch it, Random crashed and freezes and has just been acting up for no good reason. I was running CM 10.1 nightly and dont apply ant mods to it or anything like that becuase i like it simple.
When i flashed the rom i did it with gapps but they were not intalled when i boot, all i got was my SIM pin popup like i usualy get. So i re-flashed gapps and still no luck. So i said f*** it and found another build of it and copyed it to my SD Card and was going to flash it. Like i allways do i went to factory reset and all i got was a long log of cant remove lost+found and same happed when i tryed to wipe the system. and that didnt look good so i pulled the battery and booted recovery with the key press and it would get to teamwin screen but would reboot. Opened oden on my desktop, reflashed teamwin tar and that didnt help it. So i was lucky that i loaded the rom and i rebooted to recovery and am copying all my /data/media to a sdcard that i have
So can anyone give me some links to the 16GB PIT and all that jazz so i can get thing back up and running
And no i am not a n00b becasue i have been working with android and other phones long enough to know what i am doing
Click to expand...
Click to collapse
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439

mapatton82 said:
I think this is what you are looking for. Follow the guide and you will be on stock, rooted, and unlocked.
http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Iv been able to load a rom but now i cant write to the phone, i have now found a guide talking about unbricking it useing odin anf a nand erase all and thats not working eather, any story i can tell verizon so i can get a replacement today?

Update!
Iv been useing http://forum.xda-developers.com/showthread.php?t=1840030 to try to get my phone back and so far it has failed but i decied to switch computers, all my computers are now running windows 8 and i ws doing this on my development computer / server and then i switched to the last computer to have windows 7 next to my main computer and what do you know it worked, the nand erase worked and now its booting im sure i will have to re-unlock the bootloader and all but im happy now

Note 4 Edge is in a boot loop

So it has been quite some time since I've been on these forums or tinkered with any phones. I believe the last one I rooted was a Thunderbolt.
Anyways, I have recently tried to root my Note 4 Edge and I hate to say it but I got cocky and rushed through it and now I am in trouble. (I know -- stupid)
I followed this guide (http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993) and everything was working right, followed the steps and what not. Unfortunately I did not create a backup of my last known working boot (Again, stupid, I know.) Needless to say, when I went to boot my phone up it was in a boot-loop. So I tried a wipe of everything using TWRP, everything except Micro SD and internal storage. Tried it again after the wipe, I get an message from TWRP saying that I have no OS (oh, great to see after flashing a rom).
After messing with that for an hour or two just to try and get my phone "working" again I gave up on it and tried using a ROM called HyperDrive, I think it's called. Wiped everything needed before flashing the rom, installation went smoothly, no "NO OS" message from TWRP. Rebooted phone, and what do you know, another boot loop.
Its been a while since I've tried tinkering with my phone, if anyone knows of what I did wrong or knows how to fix it I would greatly appreciate it considering ill need my phone for work tomorrow.
Please, and thank you.

Of course you wiped the system so no OS, i suggest you flash the stock rom via Odin first.

Help, out of ideas. Possible mother/logic board going bad?

I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.

could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....

Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.

Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL

oneplus6 seems damaged following a failed twrp restore

So here is situation.
Phone been running 8.x version of havocos for months, however I was never fully happy due to broken usb tethering and random lockups (blue light freeze).
I decided to work on the phone 2-3 days ago, this involved doing a manual backup of all of data/media, and a nandroid backup. As well as some exports of configs in tasker etc.
I then flashed OOS stock, and nolimits, discovered tethering was still broken (yet it works with same sim in samsung galaxy s7 and hauwei).
This was the only issue tho, everything else was functioning as expected, phone was still fast.
Then I needed quick access to something that was on my phone from havocos, so decided to do a nandroid restore, this nandroid backup had all partitions ticked. The restore I also had all ticked.
The restore failed with an error 255 during data restore, I googled and found out is a nasty known bug for 2 years on TWRP, this backup was done on 3.2.3, I know now is a newer 3.3.x where this particular bug with corrupt backups might possibly be fixed.
I decided to try and boot havoc anyway but it boot looped, so I then went back into TWRP, and restored the vendor partition which was skipped. As it stopped on data, still boot looped, but also now this created a device is corrupt error on every rom boot even on stock OOS.
I spent ages trying to fix this error and during the process, discovered my phone no longer can be detected in flash boot as a com device in windows so currently the phone cannot be used with the MSM tool.
Eventually I reflashed stock using a flash-all script from here, and also put back on twrp using that script, and noticed even more issues that were not there before.
1 - phone is now much slower, stock before booted in one second after first boot, now its way way slower. Over 10 seconds so 10x as slow.
2 - I think before was a cache partition but is now gone. Supposedly these arent a thing anymore tho.
3 - nolimits zip will no longer flash with an error 1, I did exact same process as before but simply doesnt work now, the twrp detailed log right before the error 1 says "Please install the latest Magisk!" which suggests its failing to detect magisk.
4 - camera app is way slower, and OOS feels slower, laggier in general than before the problem.
5 - MTP no longer works when phone is booted up, again this is stock OOS and even if phone isnt rooted no magisk etc. But still works in TWRP. Basically the device pops up, I can see internal storage, but the size information is missing, and is no visible files/folders.
From what I can see I think my EFS is fine, I see an imei number.
I did fix the corrupted device error using a reboot command someone posted in that thread, so that error is gone now at least.

Try to flash oxygen os beta version from the official download links, let it install the stock recovery, then boot into rom, finish the installation progress by just skipping it and then factory reset it twice from recovery mode.
after doing that and finishing the setup , try to take picture and see if its saves it to gallery ( if the picture delete it self try to factory reset it through recovery for 1 more time)

I think you have figured out whats wrong, it just clicked, and I went to post and found your post so sorry no reply yet.
Indeed the problem seems to be a lack of /data/media/0
I have multiple times wiped data, and twrp has been putting files directly in /data/media, I just discovered I Cannot even take screenshots, magisk cannot download modules as well.
So I guess the stock recovery creates this structure?
Pretty shocking that twrp doesnt fix this or even have an option to. I will report back and let you know how things go, thanks.

Issue still there after stock recovery reset, wow these phones are damn hard to work with.
Also it seemed to do nothing, no settings were lost etc.

So basically stock recovery even if I choose full wipe does nothing, there seems to be some kind of lock on the internal storage that anything made by one plus is refusing to write.
I wonder if this is due to the device is corrupt message I had before where it said the device can no longer be trusted.
I can confirm that files that are on there are now visible in file manager and root explorer. But file manager can do no writes. root explorer can create new stuff but cannot delete or overwrite anything there, gets access denied.

I propose to start over again following this guide, option flash-all-partitions.bat. Helped for me.

I already stated thats already been done.
I eventually got msm working. and that luckily worked.

@chrcol ..., but you've issues

chrcol said:
I already stated thats already been done.
I eventually got msm working. and that luckily worked.
Click to expand...
Click to collapse
In recovery, format data. Problem fixed. Wipe will never fix your problem but format will.