Develop Bugs

Sani N10 bricked while modding

Hello,
I have troubles with a Sanei N10 tablet. There was a problem during an update process, and it is not able to start. The problem is, the owner tried to force in a Clockworkmod recovery and a Cyanogenmod ROM via the fastboot.exe command "fastboot flash" using recovery.img and boot.img files. The only thing I can see on a regular boot is the Sanei logo, and then a black screen.
I managed to have fastboot.exe access by switching it on with the volume-down button pressed. I can see the device if I write "fastboot devices", and I am still able to flash the individual partitions with the same "fastboot partition file.img".
I tried myself to flash a CWM recovery and a Cyanogenmod rom, but I still have the same black screen. Then I tried to get the original rom, but I used a lot of files from a lot of forums and I still can not get out of this.
I have no access with Livesuit and Phoenixsuite to restore the tablet with, they are not able to see the device (adb.exe is not able to see it as well).
Have you any clue about how could I solve this?
A friend of mine has a working tablet identical to this one, is there any way to extract the partitions in .img format and to apply them to my device?
Thank you,
Jimmy

try this one askmefast.com/How_to_do_a_factory_reset_on_sanei_n10-qna4671741.html im 10 post user so cant add link.

[Q] Device not found error

Hello,
Few days before I was able to install TWRP to my p6. But now i want to revert to stock recovery. But now problem is when I am trying to run the process, the command prompt shows error device not found!
I have installed adb, i have phone drivers installed. Phone is detected on PCHiSuite too.
It even reboots when i put the command: fastboot reboot!
just very confused to think what would be the problem! please help..
thanks!

start the connection with: adb reboot bootloader

blueIBI said:
start the connection with: adb reboot bootloader
Click to expand...
Click to collapse
It doesn't work. Shall put up the screenshots soon! I even tried ADB over wireless just to check if there is some problem with USB drivers. But it says device not found.

is unrooting needed?
My phone was rooted. Do I have to unroot before installing the stock recovery?
I repeated the procedure of installing ADB and fastboot drivers and I then followed the procedure installing the stock recovery!
now the thing is the phone is stuck permanently on huawei logo...?
Please help me out!!!
attempt 2:
when i try to force reboot, it shows failed to update and shows the stock recovery!
it shows an option to install from external memory
and also wipe/factory reset
for the same now I have put a folder dload/update.app in the external memory card.
will a factory reset will help or should I opt to install from external memory??
Current status:
I read somewhere on the same forum to delete the dload folder and create new and paste update.app.
I did that, a little bit of phone charging and then force upgrade. This time it worked!!
It was nice to see my p6 back in life!!
but one problem still exists.
When I go to mobile networks options, a dialog box appears ""unfortunately process com.android.phone has stopped"
Any solution for that??? the sad part is I cannot check the option of "Roaming Data".. I cant use net when roaming coz of that..

sal3011 said:
My phone was rooted. Do I have to unroot before installing the stock recovery?
I repeated the procedure of installing ADB and fastboot drivers and I then followed the procedure installing the stock recovery!
now the thing is the phone is stuck permanently on huawei logo...?
Please help me out!!!
Current status:
when i try to force reboot, it shows failed to update and shows the stock recovery!
it shows an option to install from external memory
and also wipe/factory reset
for the same now I have put a folder dload/update.app in the external memory card.
will a factory reset will help or should I opt to install from external memory??
Click to expand...
Click to collapse
Which cimmand does show up the result 'device not found'? If its adb devices then it shouldnt be stuck on huawei ascend logo because thats bootloader/fasboot mode in which case you should use fastbood commands, like fastboot devices. If that turns up a device with some random numbers/letters then you are good to go for flashing stock recovery.
Sent from my SM-G850F

tileeq said:
Which cimmand does show up the result 'device not found'? If its adb devices then it shouldnt be stuck on huawei ascend logo because thats bootloader/fasboot mode in which case you should use fastbood commands, like fastboot devices. If that turns up a device with some random numbers/letters then you are good to go for flashing stock recovery.
Sent from my SM-G850F
Click to expand...
Click to collapse
Hello,
What you say is right, I just realized this after too much of fiddling with my phone...! but now its enough! not doing anything until a stable international firmware is released!
the command I used was adb reboot bootloader.
Well, later I was able to resolve the issue. Just repeating the procedure (i.e installing adb and fastboot and then following the procedure in cmd prompt helped me flash to stock recovery)
Seeing the stock recovery installed was a relief.
When the USB update didnt work for the first time
>>I deleted the dload folder and created again and then pasted the UPDATE.APP.
>>force update
This worked for me...!

[Q] [HELP] Bricked Galaxy Nexus (maguro)

Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance

I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that

Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload

Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.

[SOLVED] TWRP Bootlop, no ROM installed, fastboot not detected...

SOLVED, the solution is simple, i just quickly installed the adb drivers during the TWRP screen showed up... have to attempt a few times but finally get it to works, then i flashed the rom using fastboot mode
Hey, i was in twrp and i wiped data and system, and it suddenly reboots...
after booting it shows some error messages then it reboots again in loop... i have no OS installed currently
i tried go to fastboot mode, installed adb drivers on 3 different computers each running windows 7, 8, and 10 but still cannot detect the device in fastboot mode...
anyone knows the solution ?? Thanks Before...
If video not show up, heres the link https://www.youtube.com/watch?v=FDQqBLMvD0E
See the attachment to see the error message

- download "P2a42_S048_161111_ROW_fastboot"
- Download this file" flashall.rar"
- Go to the file "P2a42_S048_161111_ROW_fastboot" and unzip it .. !!
- Unzip the file "flashall.rar" and move the file to the folder (P2a42_S048_161111_ROW_fastboot / sw )
Then Install ROM ... by fastboot mode ... and clicking on the flashall file

Permeableaxis5 said:
Don't do this if you don't want to have your phone baseband completely removed meaning no sim card function at all. I did exactly this when trying to install stock room and it deleted my baseband. Luckily I had made a backup a month before that. I restored it from the backup and the phone (sim card) started working again.
Anyways, back to the original issue. So you're saying your phone isn't recognized in fastboot? When I wipe system and data and then go into fastboot and enter "fastboot devices" it shows nothing but I can still flash files into the phone. I'm guessing this is because the phone has no 'name' due to the system wiping. So try going into fastboot on your phone, connect it to PC and open adb, and then enter the command 'fastboot flash recovery twrp.img' (download the latest version of TWRP for Lenovo P2 and rename it to twrp).
If then you are able to enter TWRP after rebooting, download stock Lenovo P2 ROM and flash it.
Click to expand...
Click to collapse
How did you make backup

i have soled it, i will edit the post, thanks for all the help

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.

how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.

Thanks for the hint, but I am not happy with the idea of someone playing with my data

1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC

Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.

Any idea? Should I give up?

If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info

Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.

Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.

If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?

So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?

Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons

MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?

You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b

I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.

Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.

Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?

Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.

Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?

Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5