I have seen some great write ups on rooting the G1 and it worked perfectly on mine. With this new Rogers update for the 911 GPS flaw I have temporarily reenabled my data from Rogers with the "Network refresh" but I know it's only a matter of time before it dies again.
This is my work phone and I can't have loss of data so I need to do this update.
I understand you need to unroot the phone to stock for this update.
Can you point me to a successful comprehensive set of instructions to do this?
I would sincerely appreciate it as I don't want to brick the phone reverting to stock. The backup I created when I originally rooted the G1 was on my USB key which a co worker lost
Any support is appreciated!
Running Cyano 4.2.12.2
1.6 Firmware
Build DRC83
Download a 1.5 rom from Android spin or here... Install it.. same way you would do a 1.6.
Make sure your on Vista / Xp and install the HTC synch software from the rogers website and downlaod the ruu update also while your there.
Once your 1.5 rom is up and running you dont have to sign in or antyhing just synch the phone with the pc.. Run the RUU update from rogers it will wipe your phone and install 1.5 factory you lose root and your 1.6 24 hours later your data will be back
I'm looking for more details, step by step because I don't want to brick the phone... the rooting steps were finite and detailed, I know I cant just reverse the steps so I'm looking for some guidance.
What I did was that I ran the RUU wizard, then grabbed the rom.nbh file from the temp directory and put it on the root of my SD card. Then reboot in HBOOT and it applied the rogers crippled piece of **** rom.
Now I'm trying to get back to rooting it and putting Cyanogen back on. no luck so far
No one else unrooting to do the update? I thought there would be more.
I still have data but I can see it going away after another sweep by Rogers...
Don't do it.
Don't.
It's not worth it. it's just as much of a piece of **** that came with the phone. Slow and incomplete. Stick to what you have, just call those morons and convince them that you have a better rom that is not affected by the bug.
turn on your GPS and call 911 just to try it, then call rogers and tell them it works.
If you install the Rogers update there's no way out as of yet. You're stuck with it.
Think about that long and hard before you get stupid like me and apply their update. Threaten to sue them, threaten to hold back payment, but don't cave in. I did and I've been up for 2 nights trying to root it again.
So what choice do we have? Help!
I called Rogers support to have my data turned back on but they told me their system is 100% automated and will only re-enable the data when they see the right build being reported.
I don't want to get stuck with this new crappy ROM from Rogers but I don't know what else to do? I don't want to be stuck without root. Do any of the admins or uber-pros have any advice?
Please take pity on us poor Canucks with Rogers nooses tied around our necks!!
call and tell them you've had it (have the pdf from rogers update page in front of you) and say if this isn't restored you're holding back payment.
They haven't killed my data since I asked for the network refresh on Monday.
I know it will happen again though.
I just want some clear instructions to unroot is all.
If u really and badly want the rogers update do as it is below, i recomend jst wait for a few daysour devs will find out something for this issue, i did the upgarde and i lost my root, and same old PoS, without a soft keyboard
Follow The steps
Upgrade Instructions for Rogers HTC Dream
Requirements:
Rogers Dream
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
1) Download the HTC_Dream_Update.zip and extract the file within, DREAIMG.nbh to the root of the microSD card.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are 3rd party applications on Android Market that can back up your applications and personal data.
3) Power off the device.
4) Remove the microSD card from your device (if you have one already installed), press in on the microSD card to eject it and then remove it from the slot.
5)Insert the microSD card with the DREAIMG.nbh on it in the microSD slot, slide it into the slot until you feel a “click”.
6) Press and hold both Power and Camera buttons at the same time until the blue/white screen appears.
The update will automatically begin installing, follow the on-screen instructions, press the trackball when prompted to press “Action”
Once the update is complete, “Press Action to Complete” will be displayed. Press the trackball to reboot the device and complete the upgrade process remove the microSD card
Click to expand...
Click to collapse
and now ur phone is upgraded and unrooted
happy upgrading
Hey guys, don't know if this is already out there, but I was on the phone with samsung about my I9000m and it's sd card failure. (they said to send it to them and they will replace it) But the main reason for this post is, He stated that it was kies that is causing the internal sd card problem. I asked when I get my new galaxy and install 2.2 on it with the kies i have will it cause the same problem? His reply was yes, under no circumstances use the old kies to install 2.2 or you WILL have the same problem. He gave me the link to the new kies software and said uninstall everything from the old kies version and install the new one and this will not happen again. So uninstall your old kies software and download this one.
wont let me post the link, but it is on the samsung website
It's not only Kies. Many users haven't upgraded anything and their internal SD cards died. This doesn't surprise me, that a Samsung employee said this. I once called Samsung and they said, "Yeah, pretty sure it was a hoax - someone accidentally uploaded a bad firmware and thats why its causing them all to die."
I flashed maybe 10 times using Odin and ClockworkMod recovery and this caused the internal SD card to die.
Apparently the new Bell firmware, JL2, fixes the issue by installing a new secondary boot loader.
He was bs'n you.I have never even installed nor used kies and I had TWO phones die on me.
Both failed within a month. First in14 days second lasted 25 or so days. Third one has been going for around 20 days now
Sent from my GT-I9000 using XDA App
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
http://forum.xda-developers.com/showthread.php?t=1280097
Please read my problem I have encountered and how I have solved, hope this helps.
After step 6 while trying to install Mango I recieve error code 801812c1.
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
theonlyremedy said:
I faced a problem while updating to Mango via Zune software.
My phone kept restarting while installing 7.10.7720.68 update. Stuck in step 8/9 for about 30 mins.
I did the following to recover, nothing worked.
1. I guess my phone got bricked, stuck in an infinite restart loop. I cancelled my update and removed the data cable. Removed battery and put it in again, tried restarting, still in infinite loop. Thanks DELL & Microsoft!
2. I read in Dell forum that I have to turn off my phone, then hold down Power Button + Volume Down + Camera button to enter PC download mode, so that I can restore it from Zune software. Trying it now.
3. Restore from Zune doesn't work, even its stuck at 0% for about 30mins.
4. After a few tries, removing battery, removing the SIM and doing some random stupid stuff, tried again the restoration seemed to work, I mean it started to restore.
5. Finally, I guessed its time for me to give up. Restoration failed with Error Code 8018009B. So its bricked for now.
6. I was greeted with this nice message from Windows Phone support tool
"Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool cannot recover this phone. Please contact technical support."
I didn't even force the update, it was regular update which I was able to start from Zune without forcing it. NOW ITS BRICKED!
7. I took my phone to Dell Service Center, those guys couldn't figure out the problem, they said its a new phone here in India and don't have any technician to fix it.
I posted the same in Engadget, I got no response from anyone, so am posting here hoping to get a solution. I at least want my phone working, I'm happy without mango.
Click to expand...
Click to collapse
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
alodar1 said:
Curious that I see no reports of install problems with Mango on the Dell....yet, especially with those coming from any of the Beta's. Has anyone seen any reports anywhere?
I'm here to report 1.
I was on Mango release build. I flashed back to 7004, and followed the update path to 7008, then 7403 then the release build.
When completed, the VP is in a reboot cycle triggered by any touch. I've done this several times.
The reboot cycle appears as follows:
The update completes with no error and the final reboot starts. On reboot, if no sim is in place, the sim error screen appears. This is normal. Touch the screen to close, forces a reboot, regardless of the update complete message.
Repeat process, this time with a sim in place, Update is installed, success messages appear in zune and on the phone. Disconnect phone, touch the screen, reboot occurs.
Repeat process. let the phone reboot until it reaches the desktop. connect via cable to zune. The device is recognized, but NO sync occurs. Go to settings/update and the current build is recognized. Restore is available, and will work.
if the screen goes dark, slide up or touch power will bring up the Lockscreen. Wifi does show, so does 3g and battery, but NO lockscreen release options are available. Again, any touch forces reboot.
I've reported to Microsoft, but was not considered serious since it cannot be reproduced.
Did the update with my HD7 so Zune, the downloads, etc are in place and working.
Getting back to 7392 is an option, so I am not dead in the water. But wanted to make sure reports of problems with the update were reported.
Click to expand...
Click to collapse
Called Dell Mobility. Even though I could restore back to previous version, they offered to replace the device, which I took.
Kind of sad though, I've never had problems with wifi or anything else on this phone. In fact the only problem ever with a VP was me dropping the thing. I'm hoping the refurb I get will also not be a problem.
alodar1 said:
Sorry to hear this....but, I think you'll be happier with Mango...About your phone...
If this was NOT a forced update, Dell may be able to help you. Microsoft has made updating 'almost' brick free. If you log into Zune, a backup is made, you're using the cable that came with dell, not using a USB hub, have a solid internet connection,and are NOT forcing the update, the blame for the problem could fall onto the update itself.
As part of a test team, I used to try and brick Windows Phones. The easiest test was to remove the cable during different phases of update. I was never able to brick the phone. Sudden power loss on the PC also was tested. Never was able to brick a phone. Apparently the download and transfer process is done in parts, meaning the update is downloaded, completed, then transferred to the phone, then installed. If the update is interrupted during download, no worries, or even transfer, no worries, reboot the phone, try again.
The process of install is done 100% on the phone so no bad cables, or shut down of internet can impact it. Even if connection between PC and phone are lost during the install portion, the message still tells you to check the phone. The install will continue.
that leaves only the relationship between the installation and the files itself. If the update package is corrupt or damaged, then it may not be able to successfully complete. If this is the case, you have an issue with Dell and Microsoft. Since Microsoft can only help you with software, I argue that you would have relief, as in possible phone replacement, from Dell.
Do you have a way of contacting Dell from India?
Click to expand...
Click to collapse
Thanks alodar1..
I asked Dell to do a service and added that I don't need an replacement. The service guy said the phone is new and they are not trained to service this, so they would only do a replacement. I'm not ready to do a replacement, they ask me to go for international warranty, moreover they replace with factory refurbished phones.
BTW, I would like to know if there is anyway to format the memory card without removing or replacing. Right now I have another problem whenever I press the power button to boot my phone it directly goes to Software Download mode, the camera button was never pressed.
While trying to repair using Windows Phone Tool, I received this error "The tool cannot recover this phone, please contact technical support", so being a little curious I fired up .NET Reflector and loaded the tool to find out what was happening, I found that the this error is thrown if the phone is not Samsung made (see attached file). Is there any similar tool for Dell Phones?
*UPDATE 1* Is there anyway to force flash without using Zune, any third party tool, Zune seems to go to restore mode and can't find my phone. I have a feeling that erasing the contents of SD card will solve the problem.
*UPDATE 2* I did the registry trick and was able to see my DVP in Computer window. But instead of one DVP, I see 2 and both have storage of 3.75 GB each. But my DVP is 16GB, both DVP are empty. Previously I was never able to see my DVP even after registry patch. Now I have feeling that corrupt drivers caused the problem, yesterday I completely removed and reinstalled Zune Software, now the registry patch worked.
Please let me know with problem my DVP could be hardware fault or just the software. If its hardware then I'll go for replacement right away.
Just recieved my replacement VP. Ordered yesterday around noonish. Went downstairs to get the Motorola Xoom box that was delivered...and the VP was there too. Bonus....
Did not come with Mango....but....there's not a scratch on this thing....not a rub, not a bump...nothing. Still has plastic in places I doubt they would put plastic after refurb. I'm wondering if I got one of hte left over new ones....
Doesn't matter....Mango won't install no matter what...so...maybe I'll try ICS.
My Mango is now Ripe..
alodar1 said:
My Mango is now Ripe..
Click to expand...
Click to collapse
Nice to hear that!
alodar1 said:
Since I flashed back to 7004, I lost the firmware updates. I noticed that the subsequent updates do NOT flash any firmware. According to MS EULA, all updates are cumulative...contain all previous updates. I have flashed from 7004, to 7008, to 7392 to 7304. During none of these flashes has the firmware been updated. the 105 firmware is maintained. I thought I read that the 7420 update included the 219 firmware....
anyone else having this problem?
Click to expand...
Click to collapse
How do you flash it back to 7392? I need to flash mine.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
not a flash, but a restore. I've always made copies of my backups ...
You an't reflash as the user above me already said, that said, the backups are stored in
=> %userprofile%\AppData\Local\Microsoft\Windows Phone Update
so for backing up your restore poiints you can copy that folder and then keep it.
theonlyremedy said:
Nice to hear that!
How do you flash it back to 7392? I need to flash mine.
Click to expand...
Click to collapse
I was just curious. I wanted to fix my phone. The backup restore didn't work. I was just looking for some way to flash it or at least format the SD Card, so that I reinstall OS and can get my phone working. After four days of trying to fix my phone, I finally gave up and sent it for service to Dell. I even copied a little bit of code from phone support tools and tried them, I was just able to get the phone details without any problem, Mango was installed in the phone, but still it didn't boot. It would be good if we find a way to touch the SD card and format it from PC, probably we'll be able to revive many bricked phones. I would be happy to join the project if some one starts it. I can write C# code.
Mine is an error during backup
Error Code 801812DC during backup
I also add new thread.
If anyone knows, please tell me what I need to do.
Some background... this phone was bought back in the day when Note 4 was about to be released. I have been the unique owner and I have treated the device with an abnormal amount of care and respect. Updates were about to come up but for my device... the bloody thing was getting said updates way too late (2-3 months later than everybody else such as UK or Poland). I grew tired of waiting so I did it, I force updated my own device using an image from sammobile.com with Android 4.4.2 using ODIN. It worked. The phone updated flawlessly in around 3 minutes it started the boot up sequence but the only difference was that the software inside was for UK not my European region which was Romania.
Fast forward... I rooted the device, did a lot of firmware tests (even after 5.0 came out, I still installed a ton of firmwares on it and they all functioned properly even if I was dealing with Android 6.0 or even 7.0) and the phone generally functioned very very well.
Now my **** up was that I wanted to reformat the phone to a 100% stock image (which I could do with ease at any given moment) and for some strange reason I ticked "Nand Erase All" and the reformat went trough... the software fully installed. My phone booted up and what do you know? I suddenly have 16 GB of storage instead of 32. I panic a little... I try to firmware upgrade a normal stock image for the romanian version of the Note 3. Stock Romanian based software for SM-N9005. Fails mid update 100% of the time me trying it well over 20 times. A bit of research, I end up realizing I ****ed up the phone seriously bad. So one guy saves me with a "repair firmware" which is named: N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware. I manage to flash the whole thing onto the phone and it works... but things are off. Apps are crashing at random, the phone is laggy at times... heck, there's a "android.media has stopped working" popping up every 2-3 minutes or even faster if I use internal storage. I can barely do anything... it also destorys the SD Card. As in, I gotta connect it to a micro SD reader to repair the micro SD from within Windows to be able to copy what's on it or even copy something on it... internal storage is zippy but again, it stops working once this android.media crashes. A few months pass, my girlfriend gives me a chance to repair the phone one hopeful last time. So I said "**** it" and I tried flashing again, the latest RO ROM for the phone. It fails mid way. I try restarting the phone and... it's bricked. It says that the software update failed and I need to connect it to Kies to update. Did just that and I find out Samsung doesn't allow the Note 3 to be emergency software updated anymore.....
I have the repair software, and another 2 different softwares. I have tried so many times to update the device using different cables and ports. Heck, I even installed Windows 7 to see if it works (until one guy told me I can install it trough VMWare and I will get the same exact result as if I were to have Windows 7 directly installed on the PC)... nothing works. My main error message is the one attached as a picture.
I tried every ODin, port and cable I could. I just... don't know what to do anymore. The phone is great but do I really have to buy a secondary display broken phone and transfer the mainboard from that phone to this one to have a "functioning" phone again or are there other options I missed out on?
Thanks for your message! I shall try to respond as soon as possible.
Search Nand Erase .
My guess is you need a service centre with a Rif box .
Sent from my SM-N930F using XDA-Developers Legacy app
I'm not sure but is it possible to flash the phone with a 32 GB pit file?
fogoticus said:
Some background... this phone was bought back in the day when Note 4 was about to be released. I have been the unique owner and I have treated the device with an abnormal amount of care and respect. Updates were about to come up but for my device... the bloody thing was getting said updates way too late (2-3 months later than everybody else such as UK or Poland). I grew tired of waiting so I did it, I force updated my own device using an image from sammobile.com with Android 4.4.2 using ODIN. It worked. The phone updated flawlessly in around 3 minutes it started the boot up sequence but the only difference was that the software inside was for UK not my European region which was Romania.
Fast forward... I rooted the device, did a lot of firmware tests (even after 5.0 came out, I still installed a ton of firmwares on it and they all functioned properly even if I was dealing with Android 6.0 or even 7.0) and the phone generally functioned very very well.
Now my **** up was that I wanted to reformat the phone to a 100% stock image (which I could do with ease at any given moment) and for some strange reason I ticked "Nand Erase All" and the reformat went trough... the software fully installed. My phone booted up and what do you know? I suddenly have 16 GB of storage instead of 32. I panic a little... I try to firmware upgrade a normal stock image for the romanian version of the Note 3. Stock Romanian based software for SM-N9005. Fails mid update 100% of the time me trying it well over 20 times. A bit of research, I end up realizing I ****ed up the phone seriously bad. So one guy saves me with a "repair firmware" which is named: N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware. I manage to flash the whole thing onto the phone and it works... but things are off. Apps are crashing at random, the phone is laggy at times... heck, there's a "android.media has stopped working" popping up every 2-3 minutes or even faster if I use internal storage. I can barely do anything... it also destorys the SD Card. As in, I gotta connect it to a micro SD reader to repair the micro SD from within Windows to be able to copy what's on it or even copy something on it... internal storage is zippy but again, it stops working once this android.media crashes. A few months pass, my girlfriend gives me a chance to repair the phone one hopeful last time. So I said "**** it" and I tried flashing again, the latest RO ROM for the phone. It fails mid way. I try restarting the phone and... it's bricked. It says that the software update failed and I need to connect it to Kies to update. Did just that and I find out Samsung doesn't allow the Note 3 to be emergency software updated anymore.....
I have the repair software, and another 2 different softwares. I have tried so many times to update the device using different cables and ports. Heck, I even installed Windows 7 to see if it works (until one guy told me I can install it trough VMWare and I will get the same exact result as if I were to have Windows 7 directly installed on the PC)... nothing works. My main error message is the one attached as a picture.
I tried every ODin, port and cable I could. I just... don't know what to do anymore. The phone is great but do I really have to buy a secondary display broken phone and transfer the mainboard from that phone to this one to have a "functioning" phone again or are there other options I missed out on?
Thanks for your message! I shall try to respond as soon as possible.
Click to expand...
Click to collapse
20 days later it happens to another guy (me)
help me save me from this mess, please, im desperate
neeharv said:
20 days later it happens to another guy (me)
help me save me from this mess, please, im desperate
Click to expand...
Click to collapse
I have tried myself. You have a chance of actually flashing it if you have the original cable that came with the phone. If not, the service is the only spot that can help.
I went to a shop and using an NS Pro box thr phone flashed problemlessly. Found out about my bad usb cable and here we are. The phone cost me 35 euros but it functions again.
fogoticus said:
I have tried myself. You have a chance of actually flashing it if you have the original cable that came with the phone. If not, the service is the only spot that can help.
I went to a shop and using an NS Pro box thr phone flashed problemlessly. Found out about my bad usb cable and here we are. The phone cost me but it functions again.
Click to expand...
Click to collapse
will this work: https://forum.xda-developers.com/showthread.php?t=2610757
it said it will fix partition corruption (like what happens when you do nand erase all without pit file)
neeharv said:
will this work: https://forum.xda-developers.com/showthread.php?t=2610757
Click to expand...
Click to collapse
Probably. Try it.
Here's the fix, it is the proper way to use "nand erase all" and to fix problems encountered while trying to use it:
https://forum.xda-developers.com/showthread.php?t=2610757
You can find the you the PIT files you need for it
https://www.sammobile.com/forum/showthread.php?t=30482
(make sure you download the one coresponding to the stock firmware just in case)
For other devices just google it.