Database Users

I effed up....

Well, I tried flashing CM7 Alpha #39 after getting Clockwork 3.0.0.1 and kept getting stuck on a boot loop. I went back to stock and flashed build #40 and now my Mytouch is stuck on the screen showing "T-Mobile Mytouch 4g" I've tried everything even flashing back to the first nanroid I made and nothing. I've waited for over 16 minutes and it hasn't gone past that screen. Does anyone have any clue what I should do? I'm not going to sleep till I fix it.....

you should try to update the clockwork to a higher version

U need cw recoveries 2.x exp. 2.512 to flash anything 2.2 n the 3.x r ONLY used for gingerbreads...u cant go back 2 stock on gingerbread recoveries so flash the 2.x...hope that helps...im tired hope u can understand me

Is that possible with me only having access to the hboot screen and he recovery screen?

From hboot you should be able to get into fastboot. With fastboot you can flash recoveries, nandroids, and images all via adb.

What would be the 2.x I need? I kind of got how to do adb I just don't know what file I need to use.

kirkcody said:
U need cw recoveries 2.x exp. 2.512 to flash anything 2.2 n the 3.x r ONLY used for gingerbreads...u cant go back 2 stock on gingerbread recoveries so flash the 2.x...hope that helps...im tired hope u can understand me
Click to expand...
Click to collapse
Thank you so much!!!!!!!!!!!!!!! I had to read it twice two get it, but once I did I knew what to do. I got to be more careful.

How were you able to download and install ClockworkMod 3.x? When I installed it via ROM Manager, it automatically installed 2.x without an option for anything newer.

TeeJay3800 said:
How were you able to download and install ClockworkMod 3.x? When I installed it via ROM Manager, it automatically installed 2.x without an option for anything newer.
Click to expand...
Click to collapse
U have to do it thru fastboot or terminal on your phone, but I could never get it to work on my phone. Flashed easily thru fastboot for me.

esincho said:
U have to do it thru fastboot or terminal on your phone, but I could never get it to work on my phone. Flashed easily thru fastboot for me.
Click to expand...
Click to collapse
Yes fastboot is very simple to use as long as you have your adb set up correctly.
1.Place the recovery.img in the "tools" folder of sdk
2. Navigate to sdk-tools folder, open command prompt here
3. Reboot into fastboot/bootloader (either through adb or holding power down and volume down)
4. Fastboot devices, and flash the recovery.... basic steps

Thanks, but I know how to install recovery images. I was asking where you downloaded the 3.x version of ClockworkMod.

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] TWRP wont start after Updating to 4.3

Hey guys,
I had installed TWRP on my Nexus 7 when it was on 4.2
Then updated to 4.2.2, and everything worked perfectly.
But now few days back, I updated to 4.3 and since the update, TWPR has stopped working.
When i go in recovery i get "!" marked Android (Photo attached).
Pls help, what should i do ?
EDIT : I have also tried flashing (through fastboot) new versions of TWRP, still no Luck !!

What you are seeing is stock recovery. You need to flash a new version of twrp
Sent from my iPhone using Tapatalk

The update flashed the stock recovery into your N7. Make sure that your bootloader is unlocked and flash TWRP through fastboot, with "fastboot flash recovery [thenameofthefile].img".

Pls read the post guys, I already tried flashing new twrp, it didn't solve the problem, that's why have posted!
Sent from Nexus 7 using XDA developers app

Nikhs said:
Pls read the post guys, I already tried flashing new twrp, it didn't solve the problem, that's why have posted!
Sent from Nexus 7 using XDA developers app
Click to expand...
Click to collapse
Hi, Nikhs...
That's kind of odd... never had any problems myself using fastboot flash to flash a Custom Recovery.
Are you sure you have a working fastboot connection? Type fastboot devices at the command prompt to confirm this. You should see a serial number, followed by the word "fastboot" (without the quotes)... something along these lines...
Code:
025d2d424bxxxxx fastboot
If you don't see something like this, then attempting to fastboot flash anything is a pointless waste of time. You could have a driver problem, ubiquitously known as 'driver hell'. This need to be resolved before you can proceed.
If fastboot flash still fails to flash TWRP, then I'm out of ideas... the only other solution I can suggest is you try flashing the TWRP .img file using either one of these two apps; Flash Image GUI or Flashify. (The TWRP .img file to be flashed will need to be either directly downloaded to the Nexus 7, or copied over to it first).
Both are pretty self-explanatory to use... just follow the on screen instructions.
I have successfully flashed both TWRP and CWM .img files in the past, using these apps, on my Nexus 7, without problems.
Although I've never used it myself, I understand that GooManager will download the most recent TWRP .img file, and automatically flash it for you.
However, the problem with all these apps is... you first need to be already rooted for them to work. So if you're trying to install TWRP in order to initially gain root access, then these apps won't be of much use to you, unfortunately... in which case, you'll have to persevere with fastboot, and see if you can get it to work.
fastboot flash recovery recovery.img should work though, and (barring driver problems) the only thing I can see preventing you from successfully flashing a Custom Recovery is a partition corruption, or some sort of underlying hardware problem.
On a final note, (and clutching at straws a little here), try a different USB port or USB cable or even a different PC (if you have one). Tech can be bizarrely capricious at times, and sometimes something as seemingly trivial as changing to a different USB port can resolve the most intractable of problems.
Hope this helps... and good luck.
Rgrds,
Ged.

GedBlake said:
Hi, Nikhs...
That's kind of odd... never had any problems myself using fastboot flash to flash a Custom Recovery.
Are you sure you have a working fastboot connection? Type fastboot devices at the command prompt to confirm this. You should see a serial number, followed by the word "fastboot" (without the quotes)... something along these lines...
Code:
025d2d424bxxxxx fastboot
If you don't see something like this, then attempting to fastboot flash anything is a pointless waste of time. You could have a driver problem, ubiquitously known as 'driver hell'. This need to be resolved before you can proceed.
If fastboot flash still fails to flash TWRP, then I'm out of ideas... the only other solution I can suggest is you try flashing the TWRP .img file using either one of these two apps; Flash Image GUI or Flashify. (The TWRP .img file to be flashed will need to be either directly downloaded to the Nexus 7, or copied over to it first).
Both are pretty self-explanatory to use... just follow the on screen instructions.
I have successfully flashed both TWRP and CWM .img files in the past, using these apps, on my Nexus 7, without problems.
Although I've never used it myself, I understand that GooManager will download the most recent TWRP .img file, and automatically flash it for you.
However, the problem with all these apps is... you first need to be already rooted for them to work. So if you're trying to install TWRP in order to initially gain root access, then these apps won't be of much use to you, unfortunately... in which case, you'll have to persevere with fastboot, and see if you can get it to work.
fastboot flash recovery recovery.img should work though, and (barring driver problems) the only thing I can see preventing you from successfully flashing a Custom Recovery is a partition corruption, or some sort of underlying hardware problem.
On a final note, (and clutching at straws a little here), try a different USB port or USB cable or even a different PC (if you have one). Tech can be bizarrely capricious at times, and sometimes something as seemingly trivial as changing to a different USB port can resolve the most intractable of problems.
Hope this helps... and good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
thanks for the help !
Problem solved,
I installed the Same version (Old version) of TWRP as i had before upgrading to 4.3
then installed the latest version of TWRP over it.
Seems like that solved the problem..
I wonder what and why and how it solved

[Q] Unable to do anything

So I got root on the phone and installed recovery (twrp). Everything seemed to work fine. I put CM on the root and did the factory reset and wipe. When I tried to install it, it said it failed. Now I cant do anything but go to recovery. When I connect it to my computer, it makes the connect sound but doesnt show up in explorer.
Just wondering if anyone can help my. Ideally I would like to flash a rom (doesnt matter which) just to get an OS back.
I tried adb, it doesnt show up in the devices list and cant use sideload (just says starting but never does.

nickmc01 said:
So I got root on the phone and installed recovery (twrp). Everything seemed to work fine. I put CM on the root and did the factory reset and wipe. When I tried to install it, it said it failed. Now I cant do anything but go to recovery. When I connect it to my computer, it makes the connect sound but doesnt show up in explorer.
Just wondering if anyone can help my. Ideally I would like to flash a rom (doesnt matter which) just to get an OS back.
I tried adb, it doesnt show up in the devices list and cant use sideload (just says starting but never does.
Click to expand...
Click to collapse
Do you have a back up you can flash too? That's a stupid question ( obviously you don't since your asking for an OS)
Are your adb drivers installed at all. Try download mode volume plus and power I believe.
Secondly what is the error. Error 7?
Corrsea's solution for error 7
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Which you would have to flash from fastboot.
Make sure your adb drivers are installed though.

Sideload newer twrp, flash rom.
Sent from my LG-D802 using Tapatalk

Try this : http://forum.xda-developers.com/showthread.php?t=2432476
It should help!

Phone won't boot?

Hello, I was trying to root my phone last night, I unlocked the boot loader that worked perfectly, easy. Nothing else went well, I was fighting with it TWRP for hours and then Magisk wouldn't install. I gave up on that and tried SuperSu... now the phone just stays on the loading screen instead of booting, It won't boot into recovery either just fastboot. Can it be fixed?

Your phone is soft bricked and can only boot to bootloader, correct?
The only solution is flashing the stock ROM of the device. You can get your device (Tissot) stock ROM from here.

I just got it to boot into TWRP, after it cycled a few times.

Well that may make it easier, you can try wiping dalvik cache then wiping data and see if that works. Needless to say wiping data is going to delete all your personal data, but since you're in TWRP recovery you can back it up.

Wiping it didn't work, I'm trying to use MiFlash I have downloaded "Tissot_9.0_V10.0.10.0.PDHMIXM_Fastboot" my phone is in fastboot. MiFlash detects it but when I try to flash I just get "can not found file flash_all_lock.bat"
How do you tell is MiFlash has successfully installed drivers, it gives me a window in Chinese?

If it's not working - I never thought it would anyway - then your only option is to flash stock ROM.
You can try using fastboot commands through cmd window, if it returns <waiting for device> or something similar then the driver isn't installed properly. Alternatively you can install the driver from here.

Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?

galaxymini1 said:
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
Click to expand...
Click to collapse
You can use any version as long as it is meant for your device. Flashing the latest version might be best option.
Happy to help.

I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.

galaxymini1 said:
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
Click to expand...
Click to collapse
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.

XDHx86 said:
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
Click to expand...
Click to collapse
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...

galaxymini1 said:
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
Click to expand...
Click to collapse
You can find that in an XDA revised article here.

I got TWRP and Magisk installed no problem. I don't know if I was just tired or it was the crap guides but nothing wanted to cooperate on my first attempt.
Thanks for all the help.