Database Develop

G1 Help

So I am stuck and not really sure what do to. I was trying to update to another ROM, not really sure what happend but now my g1 is stuck in a boot loop.
I can get to the fast boot menu and also to the recovery menu to load update.zip's. I have tried to reload the root RC but when I rename and load to SDCard Ii get something about not able to verifiy the file.
Could some one Please help to get me back on track.
Side note i was trying to load this:
http://htcpedia.com/forum/showthread.php?p=18084

So i have the RC back on my phone, but would still like to install the ROM i posted in the above URL.
In the above post this is what is listed for needs:
SPL 1.33.2005 (Called Haykuro SPL)
Does any one have a link to a Guide that will show how to correctly unstall this SPL? As i under stand it, installing this SPL is very dangeris and will brick your phone easy if done incorrectly.
An ext2/3-partition for the apps
I am pretty sure that i have this set up correctly, I should be able to just go to a prompt and type in print to see the partionts on my SD Card.
Any help or comments would be great!

Boot loop after flashing a different rom is usually caused by your ext partition. You should wipe the partition when you change ROMs. You can backup the apps on the ext partition to the fat32 partition, wip ext, then restore the apps.
Use the script in post 3 HERE
As for the DangerSPL... I wouldn't recommend it unless you want to try a hero ROM. If you still want to install it then make sure you flash the proper radio first, even if you already have the radio, flash it again anyways. Both can be found HERE

[Q] Start from Scratch....

I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.

Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App

fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.

ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.

fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.

fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU

I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?

I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?

fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.

Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.

fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos

Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.

Nexus one repetitive restarts

Hi,
everything was fine until I have performed a restart to my nexus one CM7 and then repetitive restarts started taking place. nothing recent has been done except the regular updates.
I have booted into CWM in order to restore from a previous backup but unfortunately when i enter all the options of the CWM i get a black page with the ROM manager logo.
could you please help me out on how to restore my phone, or at least how to flash a new ROM from zero via ADB or so
Thanks,

There are many ways but you really can't flash a rom easily with ADB. Read the tutorials if you need to learn how to flash a rom. But you should be fine if you just wipe and flash whatever rom you want.

Please look at Nexus One Wiki, section "Unroot/restore", PASSIMG method.
Link to Wiki in my signature.

zeekabal said:
Hi,
everything was fine until I have performed a restart to my nexus one CM7 and then repetitive restarts started taking place. nothing recent has been done except the regular updates.
I have booted into CWM in order to restore from a previous backup but unfortunately when i enter all the options of the CWM i get a black page with the ROM manager logo.
could you please help me out on how to restore my phone, or at least how to flash a new ROM from zero via ADB or so
Thanks,
Click to expand...
Click to collapse
Sounds like a corrupted sd card maybe. Do you have EXT partition? try format the sd card, new sd card or even try booting without an sd card to see what happen.
Had this happened once when i was on CWM, my EXT got corrupted and it was endless bootloop. Format my sd card, use Amon Ra to partition to Ext4 again and all was good.

No Mobile Data after Nandroid Restore

I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!

Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.

Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?

Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.

Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.

Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.

Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.

Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.

Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.

[HELP] Mi5 Doesn't Boot

The situation is a little complicated, so I'll explain step by step. I appreciate any help, idea what what caused this or if I can do anything to fix. Please, write if you have even a little clue.
- The top speaker (earpiece) was faulty. I wanted to change it.
- I damaged signal antenna port on motherboard while changing the speaker.
- Anyway, phone was working in all this process. Just no signal.
- After, removing motherboard for a second time, phone didn't boot up.
- I flashed a custom rom via TWRP. (phone was already unlocked.). Didn't boot.
- I flashed MIUI via TWRP. Didn't boot.
- I flashed MIUI via Xiaomi Flash Tool. Didn't boot.
- I am able to enter fastboot and recovery.
- It's charging, without problem.
- It doesn't stuck on kernel phase (It passes the MI screen).
- It stuck on boot screen. I have waited really long times, more than 30 minutes.
Do you think, I f***ed up the motherboard? Why it doesn't boot? Please, share if you have any idea.

@baggord
If the motherboard was dead, you'd not be able to turn on your phone.
Sounds like software to me at the moment.
Some ideas:
Are you on the latest twrp version (3.2.3-0)?
Did you try reflashing latest twrp via fastboot (not from within twrp)
and then wiped all partitions (including mounting and also wiping vendor) following a formatting of the data partition (where you need to type "yes") following a reboot to recovery?
Did you try restoring the efs partition from a backup where everything worked?
Would also rather try a stable custom ROM to test.

Hi,
If nothing worked, follow the instruction of this video. It worked for me after dropping my phone in water.
Sorry for my poor English?

Phil_Smith said:
@baggord
If the motherboard was dead, you'd not be able to turn on your phone.
Sounds like software to me at the moment.
Some ideas:
Are you on the latest twrp version (3.2.3-0)?
Did you try reflashing latest twrp via fastboot (not from within twrp)
and then wiped all partitions (including mounting and also wiping vendor) following a formatting of the data partition (where you need to type "yes") following a reboot to recovery?
Did you try restoring the efs partition from a backup where everything worked?
Would also rather try a stable custom ROM to test.
Click to expand...
Click to collapse
I tried flashing twrp via fastboot. I've also tried stable custom rom and stock rom.
I'll try to format all partitions then re flash a rom. I don't have an efs partition backup. Can I backup in this situation or do you think it's already gone?
Thanks for the reply!
Kabula2000 said:
Hi,
If nothing worked, follow the instruction of this video. It worked for me after dropping my phone in water.
Sorry for my poor English?
Click to expand...
Click to collapse
Hi, thanks for the reply. I'll check it out.

baggord said:
I don't have an efs partition backup. Can I backup in this situation or do you think it's already gone?
Click to expand...
Click to collapse
An old efs backup could have been of use, as sometimes important things like the imei get lost and you would only be able to restore it via this partition.
Next time better make an efs backup right away and store it at a safe external place in case you one day might need it.
In this scenario it's too late.
If it's faulty you only backup something that doesn't help you later.
Might still be that your problem has another source.
Then, if we found out a solution and everything is working well again, of course you could make that backup.
Please tell us if the wiping and formatting changed anything.
Good luck!

Phil_Smith said:
An old efs backup could have been of use, as sometimes important things like the imei get lost and you would only be able to restore it via this partition.
Next time better make an efs backup right away and store it at a safe external place in case you one day might need it.
In this scenario it's too late.
If it's faulty you only backup something that doesn't help you later.
Might still be that your problem has another source.
Then, if we found out a solution and everything is working well again, of course you could make that backup.
Please tell us if the wiping and formatting changed anything.
Good luck!
Click to expand...
Click to collapse
I am out of my home town, currently. I will inform you when I get back to town.
Thanks for the replies.

@Phil_Smith
I talked to my brother since I'm out of town.
He wiped all partitions including vendor.
Reboot into recovery. (format data returned error, before reboot)
Then format data. (worked fine)
Reboot into recovery.
Flashed a custom rom.
It boot up!
Thanks.
IMEI stays by the way. Now we need to fix the antenna somehow. Phone is still alive, at least. Thanks again!

baggord said:
@Phil_Smith
I talked to my brother since I'm out of town.
He wiped all partitions including vendor.
Reboot into recovery. (format data returned error, before reboot)
Then format data. (worked fine)
Reboot into recovery.
Flashed a custom rom.
It boot up!
Thanks.
IMEI stays by the way. Now we need to fix the antenna somehow. Phone is still alive, at least. Thanks again!
Click to expand...
Click to collapse
Nice, glad that you're good again!