Database Develop

USB/Charger reboot the phone, download mode lost, vibrant rom on i9000

OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?

OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.

Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...

CMR loop - streak 7 "brick" - frustrated, S.O.S7

Ok, so like many others am facing a CMR loop on my DS7.
here are my situation specifics
When I turn on my DS7 it goes straight to the dell logo and then the 3 lights on the face, (home menu back) flash and it goes straight to ClockworkMod Recovery 3.0.2.0.
Volume + and power does not load stock recovery options
Volume - and power does not load fastboot
both volume + and - then usb does not work, win 7 professional does not recognize.
i can access my internal storage via USB storage mount. if i put files on the DS7 they stay there.
I have downloaded NVFlash and the nvidia usb drivers, but am not sure where to extract them too i guess?
This situation came about while trying to flash the HC unbranded US 4G update.
I gingerbroke, achieved root through rom manager, flashed CWM 3.0.2.0, flashed update, and now here i am...
I am tech literate, and can follow directions if they are given clearly, can someone please help (and stay on track, start to finish) or share a link to a concise walk through? i know this issue has been resolved by oth er members but the process is spread across threads, sites, PM's, pdf's... and i just can't follow the trail to the grail.
sincere appreciation and thanks to anyone who is able to shed light. Thanks all.

Ok I think this is whats up. You said you flashed the HC 4g. I had this issue somewhat, what I did was this. I had CWM 3.0 like you. Flashed the HC, then CWM stops working. I used the pinhole to turn off the DS7. Then I - powered on to fastboot. Then I flashed CWM 5.0 (You need to do this using fastboot) once thats up, pin hole it off, then go into CWM again, and factory reset. Then you should be ok.
If that doesnt work. And you are still in CWM 3.0 I would suggest trying to flash the 2.2.2 with Tweaks rom. See if that restores you and dont forget to factory wipe.

Asus memo pad 7 (k013) does not start after un-root

Hi all,
I am trying to build a car headunit system using the Asus memo pad 7 ME176CX (k013). I got everything sorted out and the last thing I had to do was to kill the player when the ignition of the car is off.
For that reason I installed llama and made an event to kill the player when on battery. This did not work so I decided to root the tablet so I could force-kill the app.
I downloaded the one-click zenfone root from and followed the instructions. Everything worked just fine and I got the Super SU icon and so on.
Unfortunately, llama still could not kill the process, so I decided I did something wrong and started the un-root.bat file. The process ended with success, but.......I got stuck to the ASUS logo with the loading
indicator below (just before the home screen loads) . I could still connect to the tablet and performed the CheckBeforeAction.bat - it worked just fine. For some reason decided that it would be a good idea to root again and did it - again successfully (or so says the shell).
However, I could not go pass that ASUS logo. So (as if I haven't created a big mess already) I entered into fastboot mode and performed factory reset. That did not help at all.
I followed the instructions and downloaded the stock 182 ROM (I saw the WW version from the fastboot screen), put it in the root of my external 16GB SD card and renamed it.
Well.....when I enter fastboot mode I do not see an option involving SD card. All options I have are droid reboot, something I can not remember but has nothing to do with SD, recovery, power off.
When I go to recovery there I see
- reboot
- apply update from ADB
- wipe data
- wipe cache
Strangely, I can no longer connect to the tablet via USB, so I do not know how to make use of the CWM.
I downloaded ADB_driver.zip and ASUS_Android_USB_drivers_for_Windows_20140325.zip, but for some reason these do not work - I get ERROR 10 when starting the driver.
Well, after all the things (probably really stupid) I did, now I am still not able to boot, but it also looks like I have no more USB access to the device and do not know how to take advantage of the
procedures that I have seen in the different threads.
Is there a way to still recover the device?

Samsung Galaxy Tab 8.9 (Wi-Fi) stuck in charging screen, doesn't turn on at all

Recently, I have decided to install a custom ROM on Galaxy Tab 8.9 (Wi-Fi) and messed up everything.
I downloaded some "ICS 4.0.3 or something" .zip file to my root folder. Stupidly didn't install any ROM manager (Play market couldn't download any app in my tablet). Tried to download .apk file, and when failed, I fed up with everything: turned off the tablet, then turned it on with VOLUME UP and POWER buttons pressed. Then in the stock recovery pressed "apply update from sd card" and chose the .zip file...
...the Samsung Galaxy Tab icon was showing up on the screen the whole night. I was thinking that it's being updated and went to sleep. But I was wrong. The next day it was turned off and when I put the charger in, some stupid big charger symbol came up. I can't turn on the device and pressing VOLUME UP and POWER buttons brings me to the recovery menu, where I've tried anything (wipe user data/factory reset, reboot) with no success.
However, when the tablet is in the recovery menu, my PC sees the device through adb when i run "adb devices". I can even push some file to "/data/local/tmp" with "adb push" command. Now I want to know: can I still somehow install some ROM or at least factory reset to my tablet?
"I want to hide under some rock for a couple days until someone helps me"

gdrt94 said:
Recently, I have decided to install a custom ROM on Galaxy Tab 8.9 (Wi-Fi) and messed up everything.
I downloaded some "ICS 4.0.3 or something" .zip file to my root folder. Stupidly didn't install any ROM manager (Play market couldn't download any app in my tablet). Tried to download .apk file, and when failed, I fed up with everything: turned off the tablet, then turned it on with VOLUME UP and POWER buttons pressed. Then in the stock recovery pressed "apply update from sd card" and chose the .zip file...
...the Samsung Galaxy Tab icon was showing up on the screen the whole night. I was thinking that it's being updated and went to sleep. But I was wrong. The next day it was turned off and when I put the charger in, some stupid big charger symbol came up. I can't turn on the device and pressing VOLUME UP and POWER buttons brings me to the recovery menu, where I've tried anything (wipe user data/factory reset, reboot) with no success.
However, when the tablet is in the recovery menu, my PC sees the device through adb when i run "adb devices". I can even push some file to "/data/local/tmp" with "adb push" command. Now I want to know: can I still somehow install some ROM or at least factory reset to my tablet?
"I want to hide under some rock for a couple days until someone helps me"
Click to expand...
Click to collapse
Yes you can still fix your tablet. Put your tablet into download mode then connect it to your PC. Download and install Odin (find it here. Also download and install TWRP recovery (find it here). Open up Odin and select AP, browse to the location of the downloaded TWRP file and select it. When you've done this press start. It should install TWRP recovery to your tablet. Boot into your new recovery and Wipe system, data, cache and dalvik. Download and install this ICS ROM and push it to your sdcard. Install it as normal ROM and reboot. Your Tab should now work fine.

L3R0N said:
Yes you can still fix your tablet..
Click to expand...
Click to collapse
I've already fixed it Finally, I learned what is Odin used for, a tool all samsung noobs need. I've flashed Android ICS 4.0.4 downloaded from editandroid site with Odin(v1.85) and it looks great! Thanks for your reply though!

gdrt94 said:
I've already fixed it Finally, I learned what is Odin used for, a tool all samsung noobs need. I've flashed Android ICS 4.0.4 downloaded from editandroid site with Odin(v1.85) and it looks great! Thanks for your reply though!
Click to expand...
Click to collapse
Even the pros need Odin at times tho.so it ain't a noob tool. Glad you fixed your tablet.......in case you're up to it we got a Lollipop ROM too!!!

L3R0N said:
In case you're up to it we got a Lollipop ROM too!!!
Click to expand...
Click to collapse
That was actually my friend's device, I am really fed up with this ROM thing, so thanks but no

TWRP soft brick?

After months of deliberation I finally decided to root my Note 9. It was the first time I've ever tried rooting and it seems to have gone horribly wrong. To root the phone, I followed the guide in the video titled 'How to Root Galaxy Note 9! [EASIEST METHOD]' on youtube which has an instruction link in the description. As a new user here, the forum doesn't allow me to post links yet, so please just type the title on youtube and it'll come up as the first result.
What I did was:
- unlocking bootloader
- Flash AP file with TWRP version 3.4.0
- Wipe data
- Since I was worried about using a software from an unknown source, I then flashed the official magisk v20.4 instead of the 'N9-S9_root_for_oem_issue_devices_v3' file recommended in the video.
After doing so, the note 9 restarted and showed the error message "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.". I allowed the phone to reset.
Following this, the phone restarted and showed exactly the same message of 'verification failed' and no amount of going through the rebooting process resolved the issue. I googled the issue and was advised to flash the phone with Odin by going into download mode. I then tried to go into download mode, but the phone will simply not go into it and tries to restart the normal way. I also tried to connect to my laptop to see if I can flash with odin but the phone was not recognised at all by the computer.
I then tried to reboot using the twrp key combo and this worked. I then decided to try flashing with the 'N9-S9_root_for_oem_issue_devices_v3' file in the tutorial. Yet, this led to the same issue as with the official magisk file.
Looking at some rooting tutorials, I see that some of them recommend flashing CSC, AP, BL and CP instead of just the AP in the tutorial I followed. I then thought that perhaps the issue is I need to install a ROM on the device. I therefore tried to load the lineage 17.1 ROM in the micro SD card and installed it (top left option on twrp 'install') as well as the magisk and disable_dm_verify_forceencrypt zip files.
In hindsight, this was a stupid move from me - I did so I was in full panic mode at that point and desperate for a solution.
After doing so, the phone rebooted and showed a booting animation of a single blue curved line stuck with a circle rolling from right to left on it.
I left it for a while, hoping that it meant the new ROM was booting. 30 min later it was still stuck on the animation!
I then tried to reboot the phone. Pressing power button did nothing. I then tried different combinations and eventually power + volume up + bixby allowed it to restart in TWRP mode.
As of now, the phone is still in TWRP mode. The phone is still not recognised by my laptop and will not enter download mode if I press volume down + bixby when restarting.
I am fully aware that I've screwed up the rooting process and feel awful about it. It was the first time I've ever tried rooting and I really hope it is only a 'soft brick' and that my phone can be saved. I would really appreciate if anyone here could advise what I can do to complete the root process correctly from here?
Many thanks,
Sam

Is there a "download" or "bootloader" option when you press the reboot button in TWRP? My Note9 is on stock, so I'm not 100% certain myself. However if there is, that should take you to Samsung's download screen. This way you can send yourself back to stock if you give up on rooting your device.
BTW, I do recommend following a note9 rooting guide on XDA (it's not too hard to find) over a youtube video, since YouTube videos can often be out of date or a little sketchy.