Database Users

Help me with my US Dell ATT Streak - I'm not sure what to do

Ok, I have another thread elsewhere but it's not helping. Here's the deal.
Dell Bought AT&T Streak on Contract.
I rooted by Universal Androot and it said "woot" it worked (or something to that affect)
As far as "Update.pkg" I have used 4399 and 6941 and below is what happens (with other recoveries too, 6941 and clockwork)
I then got into fastboot and flashed recovery r1-4399-Streak-Recovery and it went well. Phone said "done"
So I unplugged from USB, took out battery, put back in and held volume/up/down and power..........chose 2
Dell logo comes up for a second then I get taken to a screen where it says
Android System recovery utility - GAUSB1A110421
Press the Shutter button to start emergency software recovery.
Warning: All data will be erased.
Press the Volume Down button to power off without recovery.
I have tried not hitting anything (which takes me to the Dell Logo eventually where it just stays stuck) and I have tried hitting the camera button which does the same (after I get a load icon)
So, since I don't have access to my phone to know exactly what stage it's in, I don't know where to start again.........Please help........I really need my phone and at this point don't care about 2.1. I have about 9 hours into this so far.........

Tried another way by using clockwork recovery 1.8.1.7 (any later versions just boot into a black screen)
I initially get Cant Find MISC: errors, but still get options so I installed build 6941 and got a few more errors.........then
install from sdcard complete
E: Can't find MISC:
so I was back in clockwork and held the camera button on "reboot" and am stuck at the Dell Logo again.............Please, I'm about to call Dell and turn this back in, I seriously need a phone........2 days with this and I think I've tried everything.........

So what do you have on there as of right now?

last thing I was able to install through clockwork was
downloaded 4399-update-streak-stock-rooted-signed.zip from http://android.modaco.com/content/dell-streak-streak-modaco-com/314313/how-to-get-your-streak-back-to-factory-condition/ and renamed the whole zip file update.pkg then through clockwork I get what's written below......
update.pkg.zip
E: cant find Misc
finding update package...
opening update package...
Installing update...
Installing system...
Writing boot image...
Install Complete!
Install from sdcard complete.
then from clockwork recovery I go to "reboot system now"
and get E: Can't find MISC:
Then it reboots and I see the Dell Logo and the Home and Menu Keys flash like crazy, then I have the Dell Logo and it just stays there (30 mins so far)
I really feel like I've tried every combination, This round it keeps flashing the home and menu keys every couple of minutes, but is still on the Dell menu.

Are you sure you're renaming it right? I don't think it should display update.pkg.zip.....

I have tried downloading just PKG files and renaming them and using stock recoveries, as well as downloading "zip" files and renaming them............given that I don't think anything has ever taken, I'm not sure what build I have anymore, or where to start?? I have seriously tried everything I can find from Streaksmart, MoDaCo, and here............I think I have too many variables going on and no way to know where a starting point is..........is there something I can do from the SD card through a reader that will help, or what...........I'm thinking I'm still on my 1.6 ATT 6061, but really don't know.

Hm, maybe try this?
HOW TO RESTORE YOUR STREAK BACK TO FACTORY CONDITION:
Option 1.
1. Download the stock recovery ROM HERE (http://hotfile.com/dl/61659279/506ac40/recovery.stock.img.html) and the stock official Dell ROM HERE (http://hotfile.com/dl/61663686/7d7e528/Streak_104_4399_21.pkg.html).
2. Rename the stock official Dell ROM 'Update.pkg' and put it in the root directory on your SD card.
3. Boot Streak in fast boot mode (hold camera button when turning on), press 'Fast boot Mode' button, wait 10 seconds then connect to your PC (must have Dell PC suite installed).
4. Open a command prompt, navigate to the folder where your 'fast boot-windows.exe' is stored.
5. Type 'fastboot-windows.exe -i 0x413c flash recovery c:\recovery.stock.img' . Make sure the .img file is in c:\ directory. The program will now update the recovery image on your Streak.
6. Once the phone reads 'Recovery Done', remove the battery and insert it again.
7. Boot Streak in Recovery mode (hold down vol up and vol down when turning on) and select option 2.
5. Wait till it installs and it'll boot into Android....DONE!
Option 2
Place update.pkg on SD card root folder
Power up streak whilst holding both volume buttons
Select option 2 - "software upgrade via Update.pkg on SD card" by pressing camera button
Press camera button again Job done
Thanks to the Guys over at MODACO for putting this together.
Click to expand...
Click to collapse

well, I've done that same thing with many different roms and images, and maybe these ones, but I'll try and let ya know.

I don't know why, but I got the O2 splash screen and it booted up...........I have flashing buttons, but that's ok for now, I'm going to figure something out from here! It's been a long two days!! Thanks!!

digthemlows said:
I don't know why, but I got the O2 splash screen and it booted up...........I have flashing buttons, but that's ok for now, I'm going to figure something out from here! It's been a long two days!! Thanks!!
Click to expand...
Click to collapse
No problem. Glad I could be of assistance!

I have 2.1 now, and it's awesome!! Not sure why folks are wanting to go back to stock....and now that the source code is out, I'm sure good things are coming!!

could you give a list of the files you used to get to 2.1?
I'm using a U.S dell streak Build 6601. Rooted with the flashing buttons. I've returned it to the stock recovery ROM because all the others and clockwork that I tried gave me the blank screen like you described. With the stock recovery and the O2 build from the post JaysFreaky mentioned gives me errors:
E: No Signature (972 files)
E: Verification Failed
Thanks!
Oh and a general question, would the official O2 2.1 update work on a rooted U.S streak? Or is it best to "start fresh" with the O2 1.6?

Okay, I'm successful now too, But I want to share HOW I achieved my success.
I followed the advice here: http //forum.xda-developers.com/showpost.php?p=7668927&postcount=6
And infact, I did so without using the custom Recovery roms, I just used the stock recovery WITH the 2.1 update, skipping the O2 1.6...be patient though, because through out the processes, there were moments I thought it was hanging, it wasn't. Also toward the last step, it sits at the O2 logo for a bit then it gives you the heavenly start up sound and you're GOOD TO GO.
Good luck everyone and happy streaking!

johnniedell said:
could you give a list of the files you used to get to 2.1?
I'm using a U.S dell streak Build 6601. Rooted with the flashing buttons. I've returned it to the stock recovery ROM because all the others and clockwork that I tried gave me the blank screen like you described. With the stock recovery and the O2 build from the post JaysFreaky mentioned gives me errors:
E: No Signature (972 files)
E: Verification Failed
Thanks!
Oh and a general question, would the official O2 2.1 update work on a rooted U.S streak? Or is it best to "start fresh" with the O2 1.6?
Click to expand...
Click to collapse
I used the recovery file from the post in this thread. and I used http://android.modaco.com/content/dell-streak-streak-modaco-com/316229/19-aug-streak-2-1-downloads-how-tos-rom-superboot-recovery/ for 6941. Worked fine, after reading all over the web though, I'm gonna say that something is "twitchy" about rooting and adding new ROMS on the streak though. I followed directions exactly from at least 6 different folks and there are still tons of questions being posted. I don't think it's peoples inability to follow directions, it's that what works for some, doesn't work for others.

video
Would anybody be willing to make a video on this I'm having a hard time witn all this

johnniedell said:
Okay, I'm successful now too, But I want to share HOW I achieved my success.
I followed the advice here: http //forum.xda-developers.com/showpost.php?p=7668927&postcount=6
And infact, I did so without using the custom Recovery roms, I just used the stock recovery WITH the 2.1 update, skipping the O2 1.6...be patient though, because through out the processes, there were moments I thought it was hanging, it wasn't. Also toward the last step, it sits at the O2 logo for a bit then it gives you the heavenly start up sound and you're GOOD TO GO.
Good luck everyone and happy streaking!
Click to expand...
Click to collapse
johnniedell: Different result for me:
I was an in the same situation as you were...
Streak US AT&T
Baseband version: unkown (used to say GAUSB1A111231-US, but not after numerous tries)
Kernel 2.6.29-perf
OEM version GAUSB1A111231
Build number 6601
Device is rooted. (Universal Andoroot)
Flashing the 4399 recovery image apparently works (says Done)
But as soon as it reboot and flash the Update.pkg (tried o2 stock 4399 1.6) I have the error message:
E: No Signature (972 files)
E: Verification Failed
After that I reboot and I'm back on AT&T 1.6. No harm done, so I've decided to try going direct to 6491 2.1.
No "E:" error message. It goes directly into loading the new ROM!!
However, after 2 reboots, it still doesn't pass the DELL logo screen!!! So I'm trying the one from Jays (apparently different from 4399 stock as the file doesn't have the same size). This time the home and menu buttons flashes all the time but I get all the way to the O2 screen and finally the Streak starts!!!!
Then I've applied the O2 2.1 6941, which at the end of the process produced a new screen with a green install progress bar and the info: DT: A3.724 Built date: Jul 7, 2010 10:03:09.
After that the system automatically proceeded to a factory reset and rebooted.
I thought I'd post my story in case it helped others!

Anyone still watching this thread?
I have an AT&T version of the Streak. I have the stuck logo, flashing lights issue. also. I think I've tried everything possible on these forums and had no luck yet. When I attempt to flash the stock rom (or any rom) it says "error in E: /sdcard/update.pkg.dec" My poor NEW Streak hasn't seen the face of Android UI in two days! PLEASE HELP ME!

Remember, O2 1.6 and 2.1 are not flashed from clockwork. Just put the Update.pkg in the ROOT of your SD card and use the stock recovery. There is not manual find for it. If you get stuck a the Dell Logo, do a factory reset and reboot.

Streak locked with Dell logo following update 2.2.
Hi guys.....Urgent I need help!!!!!!!....five days ago I have update to Froyo 2.2 (pack to baseband 00) from 1.6 in unlocked Streak to AT&T, baseband 31-US, version 6601....and now my Streak is dead and lock to Dell logo with black screen. I have intentend all recommendations in this thread and in Modaco, Streaksmart.com, etc, etc.....and nothing: my device is locked and dead,.....please I need help!!!!!!...any idea is apreciated.
Thanks.
Maurice.

I have yet to find a method or combination that works to update the new white Dell Streaks from Best Buy to any working version other than 1.6. I resolved the issue I had by flashing the original baseband and stock software back to the device. I guess I'll be waiting until there's an official update for this thing. Wear90, I would suggest you flash the original back on it and wait. Trying to get anything else is a headache of incredible proportions. Just sayin'

Can't boot nexus one or use recovery

Hello,
I come here and make a new thread after I spent the day inside various forums to solve my problem but wasn't able to.
Here is the thing I tried to install the cyanogenmod earlier today. I unlocked my N1 properly and think I rooted it properly as well. But I was unable to install the custom rom. Actually my N1 won't even boot, it's stuck on the cross image with the unlocked lock and I can't boot the recovery either. I tried to install a custom recovery, the amon ra thing, but it still freezes on the cross screen.
I assume my N1 isn't completely bricked since I can still power it up, start the fastboot mode and my computer recognize de USB connection (however ADB won't find the phone even after I re-installed the drivers).
So here I come for help to either bring back my N1 to its former stock rom or any functionning rom.
Thanks.

Try the unroot/restore guide with PASSIMG of FRG33. Look at my signature.

oh thank you !!! It worked perfectly !
EDIT : Well spoke too soon I rebooted the N1 after its apparent recover and it froze again, so I started the operation once more and while updating the files ravio_v2 was checked "fail-pu" instead of "ok"
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why

olicyr said:
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
Click to expand...
Click to collapse
You can't even get into fastboot any more?
Also, you say you followed the right steps to unlock the device and the right steps to root the device... What steps did you take exactly?

Hi,
to unlock the phone I used the oem command in the fastboot mode. Then I tried to install the amon ra custom recovery and I think that is what brought all this trouble.

Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.

It should boot up fastboot like Dirk said. You can not brick the phone by flashing a recovery.
Sent from my Nexus One using XDA App

I guess there is some HW fault - might be a recent bad sector in one of the system critical areas. It's not something you can cause with SW - unless you're flashing hboot or radio, which should have been covered in the first restore attempt, which worked.
Anyway, if it doesn't power up at all - and doesn't react to charging - try pulling out the battery for several hours, and then put it back and try again. If it doesn't work - then you're up for a warranty repair...

DirkGently1 said:
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
Click to expand...
Click to collapse
No the phone doesn't boot anything. I'll try to remove the battery and wait a few hours like said above, if it doesn't work I'm still under warranty I think

[Q] Restore Pre-Mango without a pre-mango backup... help!!!

I somehow lost the backup of my premangostate after updating to mango. I'm having issues with my device overheating and I need to mail it in to AT&T. But doesn't the Mango beta technically void your warranty? If it does, I need to revert to premango in order to send it in... what should I do? I've tried everything. I downloaded a ROM but I don't know how to use it! HELP!!

eaglesfreak53 said:
I somehow lost the backup of my premangostate after updating to mango. I'm having issues with my device overheating and I need to mail it in to AT&T. But doesn't the Mango beta technically void your warranty? If it does, I need to revert to premango in order to send it in... what should I do? I've tried everything. I downloaded a ROM but I don't know how to use it! HELP!!
Click to expand...
Click to collapse
It does void it. Flash UCJK2 ROM from here. Just tell them you didn't update.

EnderPsp said:
It does void it. Flash UCJK2 ROM from here. Just tell them you didn't update.
Click to expand...
Click to collapse
Do you think you could post a step by step of what to do? I tried going through the forum you suggested but had no luck following the steps. I'm a US AT&T customer.

eaglesfreak53 said:
Do you think you could post a step by step of what to do? I tried going through the forum you suggested but had no luck following the steps. I'm a US AT&T customer.
Click to expand...
Click to collapse
There isn't one for Focus but if you follow the step by step guide for Omnia 7 with the Focus Rom, you should be okay as it's exactly the same. Just use the Focus UCJK2 Rom instead of the Omnia7 one.
Here's the short version:
You will not need the "Samsung WP7 Flash Program" as it is included in the ROM (Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe).
Install Samsung Mobile USB Drivers v5.2
Put the phone in download mode. Make sure battery is at least 80% when you do.
Turn off the phone
Turn on the phone, holding down the Power + Volume UP + Camera buttons simultaneously.
When the phone turns on, release the power button.
A yellow triangle with an exclamation mark and a "download mode” message should appear.
(there are 2 ways to get out of this mode: flash a rom or remove the battery).
1. Copy "Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe" in a new folder and run it (Install). After running you will see these files:
signed_CSC_Cetus_ATT_i917ATTJK2.csc
signed_eboot_Cetus_ATT.eb0
signed_pda_Cetus_ATT.nb0
signed_phone_Cetus_ATT.bin
WP7 Downloader Ver 7.21 for All Device (Publish version).exe
WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe
The fhash program you need to run is
WP7_Downloader_Ver_7.05_for_Retail_Device_(Product_Force_Select_MD5_X).exe
2. Run it and load in it the files in this folder (click Phone, Eboot, PDA, CSC)
3. If the port isn't green, disconnect the phone from USB and reconnect.
You should be good to go with all this.

eaglesfreak53 said:
Do you think you could post a step by step of what to do? I tried going through the forum you suggested but had no luck following the steps. I'm a US AT&T customer.
Click to expand...
Click to collapse
I'll be reflashing my Rogers Samsung Focus yet again since I've been trying to change MMS settings so it will work with FIDO. Anyway, I'll be reflashing this weekend. PM me if you want some walk through steps.

[Q]Restoring backup after flashing rom
Hi,
I have a At&t samsung focus running 8107 and phone's power button started acting weird. If i press it nothing happen at first, then the slide down to power off appear. I would press back but it would shut off anyways. It wouldn't reboot right and usually took about 20 tries to boot it. I have two backups saved one mango beta and one for current version. The problem got worse (wouldn't boot at all unless on usb power) so i restored it to my current version backup. Everything worked but after a week the problem came back and the phone was dead. I decided to flash it to factory rom (had problems getting it to boot to rebuild) but I eventually got it to boot. The power button still did nothing. I updated it back to 8107 and tried to restore to my backup. I keep getting error code 801812E0. My question is do you have to use the same update path to restore a backup? I had the mango beta, refresh, then cleanup to get to 7720 Mango build. The second time around I used official update path. Do you think this is hardware related?
Thanks in advance

From your description, it sounds like your power button is getting stuck in the pressed position. "Always Pressed". Occasionally, when messing with it, it will release. Also, when plugged in, that forces it to start up.
Try cleaning around the button, or remove any cases/screen protectors that might be sticking it down. If that does not work, you might need to take apart to clean or replace the button. Only attempt if you are comfortable with that type of job, otherwise, send in for repair.

Thanks for the quick response. I will try that.
Also would the power button being stuck affect the hard reset menu and download mode? I can still access download mode but the hard reset menu disappears after about 10 seconds. The only way I can reboot the phone is to plug into USB power via computer and touch the metal springs where the battery connects with a tweezers.

xyzyzyxx99 said:
Also would the power button being stuck affect the hard reset menu and download mode? I can still access download mode but the hard reset menu disappears after about 10 seconds.
Click to expand...
Click to collapse
Yes. If you hold the power button in Any mode, it forces a shutdown after a few seconds.

Took the phone apart and cleaned around the button. Still won't boot, is it possible the phone's drivers to communicate with the power button are bad? And any idea why my backups failed to restore after flashing the rom?

xyzyzyxx99 said:
Took the phone apart and cleaned around the button. Still won't boot, is it possible the phone's drivers to communicate with the power button are bad? And any idea why my backups failed to restore after flashing the rom?
Click to expand...
Click to collapse
I think this has gotten off topic from the original thread. I'll send you a private message, and we can continue there. I've been around a while, so I might get into trouble keeping it going here, since I should know better.

Does anyone have a working link to download the Samsung Focus USB drivers?
All the multiupload links are down and i am stuck with a bricked phone.
Mirror or alternate link appreciated..
Thanks

NilayS said:
Does anyone have a working link to download the Samsung Focus USB drivers?
All the multiupload links are down and i am stuck with a bricked phone.
Mirror or alternate link appreciated..
Thanks
Click to expand...
Click to collapse
Download Samsung drivers from here.

Can I get the long version of flashing a Focus I917. Yes noob, if by chance there are some pics would be helpful also! Thanks in advance!

SteelLife said:
Can I get the long version of flashing a Focus I917. Yes noob, if by chance there are some pics would be helpful also! Thanks in advance!
Click to expand...
Click to collapse
Follow this post.

[Q] CM10 has sim locked my phone

Hi guys, I really need some help here.
I have just upgraded from CM7 to CM10 using CM10-20120924-NIGHTLY-mb525. and now my phone is asking for the Network Sim Unlock Code. but the Defy was unlocked when i bought it (back when it was stock rom), but this upgrade has caused me to lose all functionality of the phone. and when i tried to reload my original rom (CM7) by using the recovery tool the phone just reboots normaly and does not enter the Cyanogen Recovery Tool.
and just to clarify
Yes I have tried Hold power button --->Reboot --->Recovery, but the phone reboots as normal, I tried to reload it using the Power on and Volume Down but that needs signed firmware/rom, and i cant seem to find any signed firmware stock or custom even with hours of googling.
oh and RSD lite does not detect my phone so cant put stock firmware on that way either.
I'd really appreciate some assistance
thanks

weesol27 said:
Hi guys, I really need some help here.
I have just upgraded from CM7 to CM10 using CM10-20120924-NIGHTLY-mb525. and now my phone is asking for the Network Sim Unlock Code. but the Defy was unlocked when i bought it (back when it was stock rom), but this upgrade has caused me to lose all functionality of the phone. and when i tried to reload my original rom (CM7) by using the recovery tool the phone just reboots normaly and does not enter the Cyanogen Recovery Tool.
and just to clarify
Yes I have tried Hold power button --->Reboot --->Recovery, but the phone reboots as normal, I tried to reload it using the Power on and Volume Down but that needs signed firmware/rom, and i cant seem to find any signed firmware stock or custom even with hours of googling.
oh and RSD lite does not detect my phone so cant put stock firmware on that way either.
I'd really appreciate some assistance
thanks
Click to expand...
Click to collapse
You can try a software sim unlock here
forum.xda-developers[delete].com/showthread.php?t=1483297

itsnotmeatall said:
You can try a software sim unlock here
forum.xda-developers[delete].com/showthread.php?t=1483297
Click to expand...
Click to collapse
Thanks for the reply, but I am unable to launch the Cyanogen Recovery tool as when i try to access it the phone reboots as normal, and i cant install a fresh version as it wont use my sd card to install apps (found this out this morning), i guess I am going to have to restore my phone back to cm7 if i can

L31 bricked by flashing rollback package

Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!

Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk

Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.

Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk

Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.

Thanks! I sent you a PM.

Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.

OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??

Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore

Thanks, but the Toolkit says it can't find the device.

Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot

dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk

Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.

I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.

markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.

dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!

Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.

Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!

I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.

Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?