Hi everyone. I have a Droid 2 that I flashed Liberty on. As of yesterday, I was just fine with it but then it began to do weirdo things like repeating key presses uncontrollably and sending calls to voicemail rather than answering them like normal. So, using ROM manager I went to find a free ROM to try and also upgraded Clockwork Mod at the same time. Now, I cannot boot into Clockwork Mod and the screen is stuck on the green Android icon. I can, however, use ADB to do things but am on a Mac so most of the threads of I've read are either PC or strictly Linux related.
What I have tried to accomplish: adb push command to put another update.zip file on the sd card but shell told me that I couldn't move it to a folder (found that kinda odd)... also tried to put a recovery.img in the root folder and reboot but nothing happened... booted into the standard recovery deleted data & cache and rebooted... nothing seems to work.
I don't have a landline so I'm really, really stuck. Can someone please either tell me what to do or point me where I can get Mac specific advice? Thank you!!!
Well first off since your on a icrap why dont you have a windows VM on your mac?
Aside from that the only thing i could recommend is using the SBF file and reflashing your phone since you are having issues with clockwork and then start over reinstalling clockwork and reinstalling Liberty on your D2
Hopefully this link helps even though its for PC
http://www.droid-life.com/2011/09/0...k-to-stock-2-2-to-receive-gingerbread-update/
Honestly, that's not very nice at all. It's a very stellar machine... the answer to you question is that I've maxed out my RAM at 3GB and to run ANY VM solution requires a buttload of memory resources.
I've seen a lot of posts about SBF files but how in the world do I get it on my phone? I've tried ADB PUSH command but I keep getting told that it won't upload because it's a "folder". It's the strangest **** I've ever seen. The folder is RW so I can't imagine what it's complaining about.
Thank you for the link, though. I will indeed check it out.
Winblows doesn't recognize the device while in bootloader
I get through #5 but am stuck because damned Winblows doesn't recognize the device while in bootloader!!! HELP!!!!!
*Make sure your battery is fully charged.
1. Download and install Motorola USB drivers that fit your Windows system. [Download]
2. Download and install RSD Lite 4.8. [Download]
3. Download the Droid2 SBF file from above to your PC.
4. Unzip that file to somewhere other than your desktop.
5. Open RSD Lite, tap the “…” button, find the 2.3.20 SBF file that you just unzipped and select it.
6. Plug your phone into your computer and turn it off.
7. Boot into bootloader by holding the Up Arrow and then holding Power until the screen flashes.
Should say “Battery OK – OK to Program – Transfer Mode: USB”
8. Click the start button and allow your phone to flash 2.2 (2.3.20 Blur).
9. When your phone gets to 100% and reboots, you are all done.
10. If your phone reboots and has a bunch of Force Closes, you need to factory reset.
11. Boot your phone into recovery using ADB and command “adb reboot recovery.”
12. Run a factory reset/wipe data. Reboot your phone and accept the update.
FINALLY after a solid 11 hours of monkeying around with the blasted thing...
I have my Droid 2 back... however, I'm posting my experiences here in the event that someone in my situation needs answers:
At the time of this writing, this is the software that's available and necessary to bring your phone back from the dead:
RSDLite5.5.msi - Downloadable from here: http://www.4shared.com/file/no12cF9K/RSDLite55.html
Motorola_End_User_Driver_Installation_5.2.0_32bit.msi - Downloadable from here: http://www.mediafire.com/?71c12qc4a1svqza
VM Ware 4!!!! (Especially if you're running Snow Leopard or Lion)
Windows 7 (my version is Ultimate but I don't believe it matters what version you have)
DO NOT USE the free, open source, Virtual Box! You will be spinning your wheels needlessly and driving yourself batty for HOURS if you try. After borrowing a copy of VMWare Fusion 4, my phone was back up and running in 30 minutes...
So, use the link that fatalfury suggested (http://www.droid-life.com/2011/09/0...k-to-stock-2-2-to-receive-gingerbread-update/) and substitute the software above... you'll be back in a flash... pun intended!
Well good to hear the link i provided worked with the exception of certain files.
The only reason why i mocked the mac is because there are a lot of things Mac's are unable to do when it comes to hacking certain programs or hardware and i always have to goes back to using windows to make it work. Thats the only reason why i said it.
Also which version of vbox did you use? i usually use it from the link below. never had problems before on Mac computers.
https://www.virtualbox.org/wiki/Downloads
Completely Bricked Droid 2
I was in the process of flashing Cyanogenmod 7 onto my friend's Droid 2 and after being stuck at the boot up Motorola symbol my friend removed the battery and now it won't turn on at all. I've been searching for fixes all over the place and I can't find anything useful. I would prefer a good fix with a PC but a fix with a mac will work as well. Can anyone help me out please?
Hello,
I bought my wife one of these tablets for her birthday. It was running great, decided to root it so that I can uninstall the bloatware that was eating this tablet up after using it for a week. Uninstalled all the happy lenovo stock softs, everything is all good... Well I decided to put JB on this tablet after root stock rom was running great. I made a backup, but somehow I completely crashed the file system, and I can get into recovery VOL+ VOL- POWER, while usb plugged in. I had a hell of a time getting drivers install in windows, and also debian. Drivers are like NOT installing properly, or it will install properly in windows, then I have an error on another device etc. I cannot get past the lenovo splash screen that does nothing, and the only way I can get adb devices to recognize the device, is when it is in splash screen mode on lenovo, but NO other adb commands will work! adb shell will simply freeze terminal or dos. It will not read micro SD card when I boot recovery, linux or windows has no idea how to even read my device when I plug it in while in recovery, im about to buy her a new one. I have googled and googled for days and hours for a fix on this. If you need detail, please ask, and I will gladly give you info. Please help, my wife is super pissed.
Thanks!!!
hey have you managed to solve this problem? I think I have the same issue as you. my tablet just doesn't want to boot normally even after reloading roms.
Hi everyone,
I hope anyone can help me with this.
After trying to change lcd density with apps from the playstore.
The mojo brings me a black screen, no logo at startup, the only thing what i can do is the root procedure, it displays me " Key driver not found.." etc.. but nothing after that.
I don't know how to restore it, or factory reset it, or acces to build.prop etc.. and also i can't acces to devices via usb => computeur(adb not listed)
If anyone get an idea, it will be great.:good:
LCD density? What app did you use? Why are you adjusting an LCD setting on a device that does not have an LCD screen? Try unplugging it for 15 minutes and then plug it back in.
EDIT: I see what you did. You used LCDDensity to try to increase the resolution. Not a great idea. You probably picked some value that is way outside of what the Mojo will display. Since this app requires root you had to grant privileges to it in order to do this. I don't know if you will be able to fix it until some method if sending a recovery image to the device (and a recovery image for that matter) is revealed.
EDIT 2: Can you try this:
http://www.freaktab.com/showthread.php?12075-FOUND-MAD-CATZ-M-O-J-O-RECOVERY-MENU
If you can get to be able to choose "Yes" for factory reset maybe it will help. It's something to try.
re :Black screen
I put a windows typical keyboard and try the mojo recovery menu procedure, always same black screen.
Now i found an image.zip call "mojo-signed-ota-MO0202-WW.zip" but how to use it now, maybe via fastboot or anything else because it's only way for now that displays me something from mojoto hdmi monitor.
daves94 said:
I put a windows typical keyboard and try the mojo recovery menu procedure, always same black screen.
Now i found an image.zip call "mojo-signed-ota-MO0202-WW.zip" but how to use it now, maybe via fastboot or anything else because it's only way for now that displays me something from mojoto hdmi monitor.
Click to expand...
Click to collapse
You'll need to contact, Madcatz for support.
gwaldo said:
You'll need to contact, Madcatz for support.
Click to expand...
Click to collapse
Hi,
I've allready contact Mad Catz support and submit a ticket, we will see if they give me a way to unblock this box.
Thanks
daves94 said:
Hi,
I've allready contact Mad Catz support and submit a ticket, we will see if they give me a way to unblock this box.
Thanks
Click to expand...
Click to collapse
Keep us updated. I am curious to see what their solution is. Either RMA the unit or reveal a recovery method to you. If the latter, I am certain many folks (myself included) would really like to know!
zektor said:
Keep us updated. I am curious to see what their solution is. Either RMA the unit or reveal a recovery method to you. If the latter, I am certain many folks (myself included) would really like to know!
Click to expand...
Click to collapse
Hi,
We will see, i posted a ticket on friday, and a guy "symphatic" told me on live chat support that it would take 2-3 open days to have an answer.
I saw in another post on xda that one guy have similar problem but due a rom update i think.
I will keep you up to date with this an we'll check at the same time if they have a good technical support.
Thanks guys.
http://forum.xda-developers.com/showthread.php?p=52563100#post52563100
davhttp://forum.xda-developers.com/showthread.php?p=52563100#post52563100es94 said:
Hi everyone,
I hope anyone can help me with this.
After trying to change lcd density with apps from the playstore.
The mojo brings me a black screen, no logo at startup, the only thing what i can do is the root procedure, it displays me " Key driver not found.." etc.. but nothing after that.
I don't know how to restore it, or factory reset it, or acces to build.prop etc.. and also i can't acces to devices via usb => computeur(adb not listed)
If anyone get an idea, it will be great.:good:
Click to expand...
Click to collapse
Do not play with a build prop on a m,o,j,o it wil screw it up likely,but if you can access a terminal on the console or command it in windows/linux/mac osx etc somehow,then you can reset the screen resolution,to do that use this set of commands in a terminal for the mad catz m.o.j.o if possible: type: su ,no comma though then hit the enter key, then type: am display-size reset ,no comma though and again hit enter key.
If a terminal is accessible which i guess it should be if usb debugging option was left turned on if usb debugging was turned off before this your [email protected],but don't ask me how you do this as i am not a developer,but it would reset the resolution on the console to factory and allow it to work for sure if performed on a terminal within the console which you cannot get access to at present,but i do think it may be possible in windows over usb debugging somehow?
I found the recovery menu i covered it in a thread here,but it only says erase not erase/restore so i guess it is dangerous doing that,the other question is does root work on erase if it does restore it,and or did altering your resolution alter the build prop file which erase/restore may/may not restore to factory after such changes making erase option in recovery dangerous although you could try it but be warned it could wipe/brick the device possibly.1st try to use the commands i gave it's easier and safer to toy with.It also 100% worked within the os when i used resolution changer pro and got it stuck in a shrunken screen size you couldn't see all the icons in.
the link to the post about accessing the recovery menu is at the very top of this post #8 post, it links to my freaktab page on how to access the recovery menu,you can only use a usb keyboard for this in usb 2.0 port though to be on the safe side remove any sd card carrying data on it if you choose to erase do not erase cache etc though at a guess?To be completely safe ask what each erase option does on the site 1st otherwise you may completely brick your m.o.j.o at present it is ok but semi bricked and still would function if you can get terminal up to alter the resolution.
PHYSC-1 said:
http://forum.xda-developers.com/showthread.php?p=52563100#post52563100
Do not play with a build prop on a m,o,j,o it wil screw it up likely,but if you can access a terminal on the console or command it in windows/linux/mac osx etc somehow,then you can reset the screen resolution,to do that use this set of commands in a terminal for the mad catz m.o.j.o if possible: type: su ,no comma though then hit the enter key, then type: am display-size reset ,no comma though and again hit enter key.
If a terminal is accessible which i guess it should be if usb debugging option was left turned on if usb debugging was turned off before this your [email protected],but don't ask me how you do this as i am not a developer,but it would reset the resolution on the console to factory and allow it to work for sure if performed on a terminal within the console which you cannot get access to at present,but i do think it may be possible in windows over usb debugging somehow?
I found the recovery menu i covered it in a thread here,but it only says erase not erase/restore so i guess it is dangerous doing that,the other question is does root work on erase if it does restore it,and or did altering your resolution alter the build prop file which erase/restore may/may not restore to factory after such changes making erase option in recovery dangerous although you could try it but be warned it could wipe/brick the device possibly.1st try to use the commands i gave it's easier and safer to toy with.It also 100% worked within the os when i used resolution changer pro and got it stuck in a shrunken screen size you couldn't see all the icons in.
the link to the post about accessing the recovery menu is at the very top of this post #8 post, it links to my freaktab page on how to access the recovery menu,you can only use a usb keyboard for this in usb 2.0 port though to be on the safe side remove any sd card carrying data on it if you choose to erase do not erase cache etc though at a guess?To be completely safe ask what each erase option does on the site 1st otherwise you may completely brick your m.o.j.o at present it is ok but semi bricked and still would function if you can get terminal up to alter the resolution.
Click to expand...
Click to collapse
Yeah i saw your method,but in my case i can't acces to an adb shell (termnial) to put "am display reset" command, i'm on macos and i can't list my mojo attached via mac's terminal in adb mode, (i've done kill...start...adb server) my mojo only appear in fastboot mode (fastboot-mac devices) it seems that it can't past the bootloader.
I've found a ROM named "mojo-signed-ota-MO0202-WW.zip" but can't flash it coz i think this rom can only be applied via recovery mode (clockword etc..).
I know that in fastboot mode we can also flash a rom, it has command to do it, but need the right files(img, etc...) which is not in that rom.
I know also that we can make system.img etc... from a rom like this but i'll be laborious, coz i am not develloper too, and i just have some basics on linux distro's but if mad catz don't give me a method to unblock my box or give me a fully stock rom, i will try it.
Well, we'll see i'll keep you up to date.
Thanks.
daves94 said:
Yeah i saw your method,but in my case i can't acces to an adb shell (termnial) to put "am display reset" command, i'm on macos and i can't list my mojo attached via mac's terminal in adb mode, (i've done kill...start...adb server) my mojo only appear in fastboot mode (fastboot-mac devices) it seems that it can't past the bootloader.
I've found a ROM named "mojo-signed-ota-MO0202-WW.zip" but can't flash it coz i think this rom can only be applied via recovery mode (clockword etc..).
I know that in fastboot mode we can also flash a rom, it has command to do it, but need the right files(img, etc...) which is not in that rom.
I know also that we can make system.img etc... from a rom like this but i'll be laborious, coz i am not develloper too, and i just have some basics on linux distro's but if mad catz don't give me a method to unblock my box or give me a fully stock rom, i will try it.
Well, we'll see i'll keep you up to date.
Thanks.
Click to expand...
Click to collapse
TMK, fastboot only flash the boot rom, at least that's what in the v2 update the sys files are just overwritten, but not a rom.
I dont think fastboot can flash the nand/OS partition.
Yeah if you get a system rom and way of installing, I too would be interested.
I'm guessing it's something they can't openly distribute...
I guess it's something we can do ourselves... just have had the time to research...
daves94 said:
Yeah i saw your method,but in my case i can't acces to an adb shell (termnial) to put "am display reset" command, i'm on macos and i can't list my mojo attached via mac's terminal in adb mode, (i've done kill...start...adb server) my mojo only appear in fastboot mode (fastboot-mac devices) it seems that it can't past the bootloader.
I've found a ROM named "mojo-signed-ota-MO0202-WW.zip" but can't flash it coz i think this rom can only be applied via recovery mode (clockword etc..).
I know that in fastboot mode we can also flash a rom, it has command to do it, but need the right files(img, etc...) which is not in that rom.
I know also that we can make system.img etc... from a rom like this but i'll be laborious, coz i am not develloper too, and i just have some basics on linux distro's but if mad catz don't give me a method to unblock my box or give me a fully stock rom, i will try it.
Well, we'll see i'll keep you up to date.
Thanks.
Click to expand...
Click to collapse
The recovery menu has update from zip file so why not try it? Put the file on an sd card and see if recovery install from zip allows that 202 update to be done without being inside the os,It's going to be risky but in your case if they opt not to fix it free,and i gather they won't without charge it's not going to hurt, as you've voided the warranty any way messing without being insulting.
daves94 said:
Hi everyone,
I hope anyone can help me with this.
After trying to change lcd density with apps from the playstore.
The mojo brings me a black screen, no logo at startup, the only thing what i can do is the root procedure, it displays me " Key driver not found.." etc.. but nothing after that.
I don't know how to restore it, or factory reset it, or acces to build.prop etc.. and also i can't acces to devices via usb => computeur(adb not listed)
If anyone get an idea, it will be great.:good:
Click to expand...
Click to collapse
Hi Dave,
I had the same problem after a reboot of the m.o.j.o ...
I only could push an image on it but without success.
The hotline sent me this link :
http://www.freaktab.com/showthread.php?12075-FOUND-MAD-CATZ-M-O-J-O-RECOVERY-MENU
But the keyboard was not recognized.
I think the best way is to push all the rom "mojo-signed-ota-MO0202-WW.zip" on it.
Because the image is only 6Mb against 240Mb.
Do you fix it ?
TE=French_Dev;52669246]Hi Dave,
I had the same problem after a reboot of the m.o.j.o ...
I only could push an image on it but without success.
The hotline sent me this link :
http://www.freaktab.com/showthread.php?12075-FOUND-MAD-CATZ-M-O-J-O-RECOVERY-MENU
But the keyboard was not recognized.
I think the best way is to push all the rom "mojo-signed-ota-MO0202-WW.zip" on it.
Because the image is only 6Mb against 240Mb.
Do you fix it ?[/QUOTE]Yes that's my freaktab page i made lol.But it's going to have to be usb not a ps2/usb adaptor,it does work trust me if your using usb 2.0 port it works with a usb keyboard,the only time it won't is if your not 100% right in how you press the keys.
can get it on my usb keyboard a cheap 5 quid generic keyboard,so i seriously doubt you can't.Unless your pressing the order of the key differently
you need to :boot from cold with keyboard in 1st read bottom paragraph then start step 1.
Step 1.1st press alt then print screen and then i hold them in as you are pressing them in that order after turning on the m.o.j.o before the light comes on though not after it will not work if you do that,doit very quickly
Step 2.Then you see the blue light appear release and repress i key holding the rest down still keep i key held in for 5 seconds release press again for five seconds release press down for 5 seconds keep doing that until white writing appears keep those alt and print screen keys on all the time whilst doing the 5 second press of i key,until white writing appears.
Step 3.Once done you'll land at a broken robot screen tust me you can do it,once there you need to press the windows symbol key hold it on, then press the print screen key hold that on as well keep both held on and finaly press home key this means you have all 3 keys held in now press down arrow with the keys held on if not working press up arrow with all 3 other keys held on.You will 100% go to the recovery menu i guarentee that.
JOB DONE
VERY IMPORTANT NOTE:
If it doesn't work turn the console off at the wall and then leave a bit turn back on then repeat until it works keep doing that,it maybe the keyboard isn't picking up if you use reboot in comand or if your using a reboot tool to reboot it use the power for the mains to turn it off on not a reboot command,it needs to be done from a cold boot.
Re
H guys
Bad news for my mojo.
First of all, mad catz did the same thing as French_Dev (Salut à toi le français), they sent me the PHYSC-1 method to recover my mad catz.
After that i have retry the method with another keyboard, and i thought i recovered it coz i was able to see the android logo(robot screen broken), and recovery menu, but impossible to have access to data factory reset.
And now Ladies & Gentlemen...
I give my mojo to a friend who sometimes unblocks android phones, thinking he will find the way...
But he bring's me back the mojo now bricked, no blue logo at startup, and no access to fastboot mode with the male male usb cable.
He told me that he finds an another rom tu put on it, but after cleaning and flash it ===> bricked...
I can i confirm that the PHYSC-1 method work, but in my case i couldn't apply data/factory reset or maybie it's coz keyboards which i have.
Now i must find the way to unbrick it if it's possible. (i think it's possible for sure, linux based...)
Thanks for all your replies guys.
daves94 said:
H guys
Bad news for my mojo.
First of all, mad catz did the same thing as French_Dev (Salut à toi le français), they sent me the PHYSC-1 method to recover my mad catz.
After that i have retry the method with another keyboard, and i thought i recovered it coz i was able to see the android logo(robot screen broken), and recovery menu, but impossible to have access to data factory reset.
And now Ladies & Gentlemen...
I give my mojo to a friend who sometimes unblocks android phones, thinking he will find the way...
But he bring's me back the mojo now bricked, no blue logo at startup, and no access to fastboot mode with the male male usb cable.
He told me that he finds an another rom tu put on it, but after cleaning and flash it ===> bricked...
I can i confirm that the PHYSC-1 method work, but in my case i couldn't apply data/factory reset or maybie it's coz keyboards which i have.
Now i must find the way to unbrick it if it's possible. (i think it's possible for sure, linux based...)
Thanks for all your replies guys.
Click to expand...
Click to collapse
It would be bricked he's attempted some or should i probably say has likely flashed clockwork mod or some rom for eg.a samsung phone or nexus tablet etcetc.Which they don't work for any other tablet or phone because they are device specific,hence the need to flash only a zip file in recovery and only a zip file from mad catz not any other rom or backup is made for a m.o.j.o except the mad catz m.o.j.o 202 update zip file so nobody should try anything else like erase etc only flashing the provided update from mad catz at a guess it won't need previous cache erase or any other erase because the zip when inside the os seems to fromat it for you so should do the same in recovery mode in theory to.Try all over again to get to recovery with a usb stick plugged in somehow with the 202 update on if possible,i am of the 'assumption' that is how it is done with a usb stick in usb 3.0 port with the zip on it but not 100% i have never done it nor do i need to chance a rick of a working m.o.j.o mate? Really feel for you though it can't hurt to tinker with it some more though now can it?
OK sorry ,may have misread a bit there,so before giving it a mate you did flash the 202 update file yes/no?
Secondly if you did flash it it tried to boot logo the lot yes/no?
Thirdly you gave it a mate who [email protected] it up for you yes/no?
Sorry i see what you mean now,you don't erase you flash the zip 202 update zip job done mate that's all no erase no nothing else to do barr that i am guessing,but you need it on usb stick or think about this,if it was downloaded on the m.o.j.o prior this 202 update zip and you click update from zip in recovery menu,i think it may ask where giving you the choice to look for the file on what ever device it may be on including the console,so you may not need a usb stick?
Perseverance is the key if at 1st you don't succeed try try and try again trust me i have used that motto to my advantage many times it's the only thing i learned from school.
That's how i found that recovery menu,it's how i found my tv secret menu last night,it's how i found all necissary flash files for and flashed a haipi phone,how i flashed my mates bb 9820 curve etcetc,i never stop trying,i have recovered iphones before and that haipai when bricked etctc so you have nothing to loose in persistantly trying it again and again until you have found the way to flash it over with 202 update.zip
I always find ways to mod (hack) devices on my own from what i label as ethical hacking although it's not the real terminology but it sort of is in a way,i basically scour forums finding bits here and bits there puting them together to find the complete path to flashing something,i may resort to taking one sentance in a forum then another then another finaly i get the full guide and i flash it,so my view is it's a sort of ethical hacking it's diuling infromation to perform a hardware hack in an ethical way as modding a rom is legal 99.9% of the time.
It's how i managed to get pi****u on a k-r42android tv box and then upgrade it to ubuntu trusty tahr 14.04 by looking at ubuntu forum posts for commands to upgrade the installation,the reason was it's ubuntu on pi****u os so therefore it can be upgraded as is done in ubuntu.So the story goes where there is a will there is a way.
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
phnxnvrdies said:
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
Click to expand...
Click to collapse
UPDATE STATUS - If I plug it into the pc without the battery i get a windows driver install box that says "Installing APX..." does this indicate the NVFlash is corrupt or is there a way to get out of apx mode.. im not familiar with that mode .. only ADB & fastboot..
Update 2 - After reading lots, I've come to conclude its hardbricked, must have had an error in memory or whatever.. its stuck in APX mode so im going to replace the whole MB with a working 32GB [model me370t] & start over .. maybe ill not install so many ROMS via multirom.. just a few - THREAD BE CLOSED - I'm done here, good luck to anyone with similar results
Hi all,
I made a really dumb mistake, a while ago I installed TWRP on my nexus 7 then downloaded and flashed Nethunter onto it (and no I didnt take a backup first, which was really silly), for a while I have had some issues with updating it, so after a few days of googling and not getting anywhere I thought the best course of action was to re-flash it. I then made another stupid mistake of formatting everything first only to find I had removed the ROM file from my Nexus.
So, I am now in the situation where I dont see a way I can get the ROM onto the device as it has no OS and doesnt power on (just get the Google Logo and doesnt go any further) I have tried inserting a USB external drive via the USB OTG port but the drive just makes a funny whirring noise and doesn't power on properly. I was going to try a USB key just to see how that would fair.
Can anyone offer any advice on how I can get the ROM onto the Nexus?
Thanks
Did you already try to boot into bootloader (vol- & power)? Probably you need to keep the buttons pressed for round about 20 sec. If you are getting there you can most likely go on, otherwise it will become more complicated.
actually managed to sort it, I found that I could side load the ROM using ADB, backup and running now
bugs789 said:
Hi all,
I made a really dumb mistake, a while ago I installed TWRP on my nexus 7 then downloaded and flashed Nethunter onto it (and no I didnt take a backup first, which was really silly), for a while I have had some issues with updating it, so after a few days of googling and not getting anywhere I thought the best course of action was to re-flash it. I then made another stupid mistake of formatting everything first only to find I had removed the ROM file from my Nexus.
So, I am now in the situation where I dont see a way I can get the ROM onto the device as it has no OS and doesnt power on (just get the Google Logo and doesnt go any further) I have tried inserting a USB external drive via the USB OTG port but the drive just makes a funny whirring noise and doesn't power on properly. I was going to try a USB key just to see how that would fair.
Can anyone offer any advice on how I can get the ROM onto the Nexus?
Thanks
Click to expand...
Click to collapse