Database Users

[Q] Boot Problem

I have a ViewPad running VegaBean Alpha 2and I've got a strange problem. The tablet boots at first boot, but when i reboot it or power it off and then on, it won't boot. It happend in VegaCream RC2 too. Is this a partition problem, or what? Is it any fix, or should I just install Honeycomb?
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!

2minuutes said:
I have a ViewPad running VegaBean Alpha 2and I've got a strange problem. The tablet boots at first boot, but when i reboot it or power it off and then on, it won't boot. It happend in VegaCream RC2 too. Is this a partition problem, or what? Is it any fix, or should I just install Honeycomb?
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Click to expand...
Click to collapse
Use moddedstock version 1 as a base, boot to CWM recovery, wipe everything except the sd card, install vegabean from CWM.
It should be OK with moddedstock version 1 as the base.
Good luck

Backlight on, Won't boot and won't go into Recovery Mode
Hello all,
Has anyone else encountered this issue where the backlight comes at power up, but tablet won't boot, also won't go into recovery mode?
I am a basic user and have read the threads up and down all evening. Sorry, if this is an easy problem to fix, I just feel like an idiot. How do I enter recovery mode now. Tablet ran fine for three weeks and this is the very first time I have seen a problem.
Running VegaBEan Beta1 on Viewsonic 10s.
Thanks!

SeanSZ said:
Hello all,
Has anyone else encountered this issue where the backlight comes at power up, but tablet won't boot, also won't go into recovery mode?
I am a basic user and have read the threads up and down all evening. Sorry, if this is an easy problem to fix, I just feel like an idiot. How do I enter recovery mode now. Tablet ran fine for three weeks and this is the very first time I have seen a problem.
Running VegaBEan Beta1 on Viewsonic 10s.
Thanks!
Click to expand...
Click to collapse
The problem may lie the layout of the partition.
This is what's been written in the VegaBean thread:
"Before installing the ZIP file make sure that:
- You have the correct partition layout (if you have VegaCream installed, you have the correct layout)..."
Install VegaCream first with from this link:
http://www.mediafire.com/?z7r5zve13ay5qc6
It's installing through nvflash so you need to boot up in nvflash mode.
It formats the partitions to the right size, and VegaBean is based upon that layout.
After that you may just install VegaBean through CWM as usual, be sure to do a factory reset before you install it.
Hope this will help you!

Phone Bricked? Please help

So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.

cfdp said:
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
Click to expand...
Click to collapse
if you can get back into recovery, you should be able to press "restore" assuming you backed up your previous ROM.

cfdp said:
So I rooted my RAZR M using motofail2go, and all was well.
Installed 'RAZR-M-Safestrap-3.12', as I was going to flash a custom ROM. I first backed up my Original Rom using the backup function.
I then wiped 'System', and went to flash the new ROM, but the flash did not work, so I restarted.
Now the problem is when the phone reboots, it showes the Safestrap splash screen with the Recovery option and start normal, but it is not working, as not sensing my inputs or something, after about 5 sec it goes to a blank screen and sits.
I tried to hard boot into the Android System Recovery, and tried to download an official Verizon ROM and install using 'apply update from external storage' using my micro sd, but I keep getting an error E:signature verification failed.
Does anyone know where I can find an official ROM to set it back to normal so I can use my phone again?
Thanks in advance.
Also: My phone originally had 4.0.4 version.
Click to expand...
Click to collapse
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.

Coronado is dead said:
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Click to expand...
Click to collapse
Dude, you sir, are a life saver. I couldn't find the info that the link you just posted anywhere. Now I can fix my phone, lol..
Sent from my PG86100 using Tapatalk 2

Coronado is dead said:
What you might want to to is use RSDlite and flash that image you downloaded. This seems like it would help you, though I have not personally tried it:
xxxx
EDIT: And once the flash is complete, I would reboot into recovery again and wipe data and cache and then let it boot into the phone.
EDIT 2: Oh, and in addition to RSDLite, you will need the Motorola USB drivers so your computer can see the phone over USB.
Click to expand...
Click to collapse
Sorry xda wouldn't let me post, reCaptcha wasn't working for some reason. Realized your link wasn't allowing me to reply lol
Anyways, Thanks a lot, that got me back up to stock and working, and I was able to reflash a custom rom (flashed to Rom slot 1, then backed up, and recovered into the stock slot). :good:

[Q] Nexus 7 stuck on google screen boot

Yes i know. I ****ed up. But somehow i was tinkering and managed to delete the entire internal storage. I can still get into fast boot and.twrp. Can someone please help me?
What was i trying to fix? Check my other thread about the headphone jack.
Edit:Also. Twrp says i dont have an os above every swipe screen...

AW: [Q] Nexus 7 stuck on google screen boot
Have you tried reflashing stock?
Sent from my Nexus 7 running Android 4.2.1

If you have an OTG cable and a USB key you should be able to make ROMs or other backups which you preserved OFF THE TABLET available to TWRP.
If not, take the above poster's advice and install pure stock to copy stuff (ROMs, recovery images, etc) back on to the tab via MTP.
I too blew away all of /data once with that "format data" button in the touch version of TWRP; I feel your pain.

Um.....I may have made a mistake and swiped on all the clear screens...including internal memory...so...T_T Am i screwed???

JoshuaXedos said:
Um.....I may have made a mistake and swiped on all the clear screens...including internal memory...so...T_T Am i screwed???
Click to expand...
Click to collapse
You're not really screwed, you should be able to flash another ROM from recovery.

As long as you can get into fastboot, you'll be fine. The easiest way is to download and install Nexus Root Toolkit, then use the "back to stock" part to flash the factory image following the instruction.

I have got something even worse
My nexus 7 tab started freezing during use and then after booting in safe mode and wiping cache in recovery mode it now doesn't even go past the google screen. I haven't even flashed anything to it at all and it's showing these crazy symptoms (The bootloader is still locked and the device is not even rooted). I still have access to the adb sideload mode and fastboot but I am confused af as to what has happened
Any ideas guys?

[HELP] Bricked My U8800 [15Feb2013 Update]

Now, I dont usually open threads, but I have an issue here. I've searched and read a lot on how to recover the U8800 in case its soft-bricked, but I've tried the reflashing 2.2 method (Fails in about 5 seconds), Linux method (blefish's method, buzzcomp's method could not yield any results. I connected the phone in the bootloader mode (pink screen) to a Linux PC, but it doesnt appear as a new device there.
Then I tried to upgrade to 2.3, it installs fine, automatically enters recovery (formats data, cache etc), reboots a lot of times (bootloop?). So now whenever I on my phone, the Huawei logo just keeps flashing.
I've also tried to replace the files when connected in the pink screen by replacing the boot.img , recovery.img, amss.bin , EMMCBOOT.mbn file, yet it bootloops.
Prior to this, I had downgraded from Aurora to the stock 2.2, which worked fine. Then I replaced the stock recovery with CWM (the correct one, not the U8800 Pro's). I did the usual clearing of cache, data, formatted system, wiped dalvik cache in order for me to upgrade to a new ROM. Everything went downhill from there
UPDATE : I managed to get 2.3 to be installed. But everytime I enable "USB Debugging", upon the next reboot, there will be a lot of apps which closes unexpectedly, like the Huawei Launcher, Google Framework etc etc. I've tried B526 and B528, but everytime I have "USB Debugging" enabled, this happens. It works fine on 2.2 though
UPDATE 2 : After my fresh installation of the official 2.3, I'd changed the launcher to Holo Launcher, but it fails at starting up. If it does, it keep saying that Holo launcher has closed unexpectedly. The only way to fix it is to boot into recovery and wipe data.
Any help?

bump

U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium

yusopa said:
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
Where can i find the stock partition flash file?

I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....

I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
Click to expand...
Click to collapse
hey i have this same mistake, i have the first boot fine after installing the official rom, but when i reboot the phone in normal boot (diisable fastboot) the phone gets bootloop, so i can't root it in order to put a new rom. i've downgrade to 2.2 froyo and get sum errors after installation but seems to work fine with 2.2 (can even root and install cwm).
after this i try again to upgrade to 2.3 official gingerbread, fist boot is fine, but when i reboot i get again stuck in bootloop... pls help

I am having the exact same issue, does anyone know how to fix this?

The problem is solved？

zgulia22 said:
The problem is solved？
Click to expand...
Click to collapse
I dont know for sure. I flashed another B528, same issues. Tons of FC messages.
I flashed an older B517, installed CWM, flashed DZO's excellent Aurora 5.0, and everything seems fine, for now.

[Q] Wiping didn't work, messed up restore - now can't boot into TWRP

First time flashing CM, and I may have messed up.
I rooted, installed TWRP, everything went perfect. I made a backup, and then tried to do a factory wipe. The wipe ended with the messages "unable to mount /system", "... /cache" and another one. I still tried to flash, and it just immediately got stuck, nothing happened. I rebooted, and everything worked fine. It was the Samsung stock image and all my apps were still there. I'm assuming it just didn't wipe at all.
I then went full retard mode, and tried to do a restore. I wanted to be sure my phone wouldn't fail on me in the recent future because some random stuff may have been partially wiped or something. Feel free to tell me I have the IQ of a chimp.
This completely messed things up, as it just got stuck at "Restoring System...". Eventually I restarted it with the power button. Now it can't boot normally, it can't boot into recovery mode, which just leaves download mode.
Any way I can fix this and subsequently install CM properly? I'm using TWRP 2.6.3.0. I've been told it's recommended to use 2.5, as the other version may have some issues (including not being able to recognize partitions). Only download mode still seems to work, so maybe there's a way to flash my phone back into the living world?
Versions:
Team Win Recovery Project 2.6.3.0
CyanogenMod 10.1.3 (RC2 jfltexx)
Thanks!

No idea really but maybe try to flash default rom/recovery etc with odin?

I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Sent from my GT-I9505 using XDA Premium 4 mobile app

HANDSY said:
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Click to expand...
Click to collapse
I got the Samsung stock ROM of july, flashed it using download mode, and everything was back! I then rooted it again, and installed CMW (see versions below). I went into recovery, and tried to do a backup. It told me it failed: "Error while making a backup image of /data!". I then wondered if it may have been due to a lack of storage (which could very well be, as that was the issue before and the old backup by Teamwin was probably still on it somewhere), so I rebooted my phone. That's when it just failed and kept showing the Samsung logo at boot. I tried flashing my ROM again, again the logo. Then I did a factory reset using the regular recovery (cache and data reset), which fixed it. Now all my apps and data are gone, but that's no problem.
I'm back at the unrooted Samsung stock image now. Any ideas what I did wrong? These were the versions I used:
CF-Auto-Root-jflte-jfltexx-gti9505
i9505-cwm-recovery-6.0.3.2(0611)
Odin3 v3.07
I did nothing more than root, install CMW, try a backup and then it all went to ****. I'm surprised a backup can even do that.

Mmm I'm not too familiar with the internal workings of backups. Perhaps something was corrupted during flashing? Glad to hear that you have got your phone working again. There is an updated version of CMW somewhere in the original development thread.
Sent from my GT-I9505 using XDA Premium 4 mobile app

i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.

Chillzone said:
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Click to expand...
Click to collapse
I tried CMW 6.0.3.6 and the Google Play 4.3 ROM as you said, and it works perfectly! I didn't try a backup this time, as it didn't exactly have anything to back up anymore.
Finally my precious vanilla Android again, I missed it since I switched from my Galaxy Nexus to my S4. Thanks a lot guys!
Edit: I do seem to be having one issue. Quite frequently after it's booted, and I enter the SIM pin, the message "Unlocking SIM card..." stays there indefinitely. I can use the phone but the message covers everything up. This doesn't always happen, but quite often. I've read some ROMs can't handle SIM lock, like CM. This is a Google Play edition, however. Is it normal that this doesn't work?
I can seem to fix it by holding the power button, and choosing "Unlock SIM" from the menu. I guess it's not that bad as I don't often reboot my phone.